You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/how-to-run-simulated.adoc
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -307,6 +307,17 @@ Once everything is up and running, you can use the system in a few ways:
307
307
* Use the browser-based console. The Nexus log output will show what IP address and port it's listening on. This is also configured in the config file. If you're using the defaults with `omicron-dev run-all`, you can reach the console at `http://127.0.0.1:12220/projects`. If you ran a second Nexus using the `config-second.toml` config file, it will be on port `12222` instead (because that config file specifies port 12222). Depending on the environment where you're running this, you may need an ssh tunnel or the like to reach this from your browser.
308
308
* Use the xref:cli.adoc[`oxide` CLI].
309
309
310
+
You can authenticate using a username of `test-privileged` and a password of `oxide`.
311
+
312
+
If the console endpoints are returning a 404 run `cargo xtask download console`.
313
+
314
+
Initiate a cli login using
315
+
316
+
[source,text]
317
+
----
318
+
$ oxide auth login --host http://localhost:12220
319
+
----
320
+
310
321
== Running with TLS
311
322
312
323
When you run the above, you will wind up with Nexus listening on HTTP (with no TLS) on its external address. This is convenient for debugging, but not representative of a real system. If you want to run it with TLS, you need to tweak the above procedure slightly:
0 commit comments