Add sidebar navigation and global command search
This commit is contained in:
@@ -46,13 +46,13 @@ Proxy the HTTPS address to controller port 3000. Open the dashboard and follow
|
||||
`.env` and run `docker compose up -d` to recreate the controller. Setup stays
|
||||
closed once an account exists.
|
||||
|
||||
Add other users under **Administration → Users**. The
|
||||
Add other users under **Admin → Users**. The
|
||||
[access guide](authentication.md) explains roles, proxy configuration, and
|
||||
password recovery.
|
||||
|
||||
## Prepare a game host
|
||||
|
||||
1. Open **Library → Game Files** and upload the complete local folder for T5 or
|
||||
1. Open **Releases → Game files** and upload the complete local folder for T5 or
|
||||
T6, including DLC. Uploads can run before any host is enrolled. The latest
|
||||
verified upload becomes that game's default files.
|
||||
2. Open **Fleet → Hosts → Add Host**, configure the host's game-port range and
|
||||
@@ -67,7 +67,7 @@ base game files; each instance has its own writable data. See
|
||||
|
||||
## Launch your first server
|
||||
|
||||
1. Save Plutonium server keys in the T5 or T6 pool under **Administration → Keys**.
|
||||
1. Save Plutonium server keys in the T5 or T6 pool under **Admin → Keys**.
|
||||
2. Open **Create server** and choose a game and map. Readiness checks run
|
||||
automatically. For a reusable lineup, use **Fleet → Collections** instead.
|
||||
3. Resolve any launch blockers and choose **Launch server**. Provisioning queues
|
||||
|
||||
Reference in New Issue
Block a user