josh/electric-cherry
1
0
Fork 0
Code Issues 18 Pull Requests Actions Packages Projects Releases Wiki Activity

Simplify single-server launch flow

Browse Source
This commit is contained in:
josh
2026-10-07 13:56:42 -04:00
parent bd7d1ed86f
commit 2e1e5ea35f
9 changed files with 670 additions and 204 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/guides/collections.md
+32 -23
View File
@@ -139,22 +139,28 @@ Every server links to its Provisioning operation timeline and recovery options,
and each child operation links back to its collection launch. Individual operations
remain visible in Provisioning activity and history.
## Create and review a single-server launch
## Create a single server
1. Choose **Single server** on Provisioning (or the deploy action on the fleet).
2. Choose the current promoted setup and select a game/map, or select a collection.
3. Choose **Preview launch**. Review the image reference, configuration sources,
managed files and versions, selected map, lobby, port, and prerequisite checks.
4. The launch automatically uses an available key from the game pool. If none is
available, manage the pool under **Administration → Keys**, then refresh the
preview.
5. Choose **Launch server** and follow the operation to verified health.
1. Open **Create server** from the fleet or **Single server** from Provisioning.
2. Choose a game and map. The dialog automatically checks the current promoted
setup, latest game files, available lobby, and game key pool as selections change.
3. Review the readiness summary and resolve any displayed blockers. When no game
key is available, open **Administration → Keys** and add one or wait for a key
to be released. Returning to the launch dialog rechecks availability; **Retry checks**
also runs the checks again.
4. If needed, expand **Advanced settings** for runtime and network overrides.
Expand **Setup details** to inspect the image, configuration, managed files,
game-file upload time, and internal server ID.
5. Choose **Launch server** in the persistent footer and follow the operation to
verified health. **Cancel** closes the dialog without creating a server.
A preview lasts 30 minutes. It reserves neither capacity nor a key. If
another launch takes the lobby, submission stops before reserving a key;
refresh the preview and review the newly assigned ID. Pool availability is checked again at
submission, and keys are reserved atomically so concurrent launches cannot share
a credential.
The single-server dialog uses the current promoted setup. Create and launch
collections separately from **Fleet → Collections**.
Automatic checks reserve neither capacity nor a key. The reviewed preview lasts
30 minutes. If another launch takes the lobby or key, submission stops; retry the
checks before launching. Pool availability is checked again at submission, and
keys are reserved atomically so concurrent launches cannot share a credential.
Host selection, game-file versions, runtime configuration and lobby availability
are checked before queueing. Provisioning assigns host capacity and physical
@@ -165,9 +171,11 @@ verify the engine map, not the variant's start location.
## Save and reuse a collection
Expand **Make this a reusable collection** in a launch preview and give it a name
and optional description. You can save the map even when host configuration or
available capacity blocks launching. Names are unique without regard to case.
Choose **Create collection** under **Fleet → Collections**, give it a name and
optional description, and add maps with their desired lobby counts. A collection
can contain a single map with a target of one lobby. You can save it even when
host configuration or available capacity blocks launching. Names are unique
without regard to case.
Each map in a collection retains the game, exact map variant, and desired lobby
count. Image references, managed files, and composed configuration are resolved
@@ -178,11 +186,12 @@ Use **Conform fleet** on a collection card to review missing servers. Remove a
collection from the library when it is no longer needed; its existing servers,
reviewed previews, and deployment history remain intact.
On a creation detail page, **Launch again** selects the original game and map
with the next available lobby and port, using the latest promoted setup. The
preview also lets you save that map as a collection with a target of one lobby.
The recorded files remain visible as deployment history. Older deployments
without a recorded recipe retain their history but cannot offer this action.
On a creation detail page, **Launch another server** opens the single-server
dialog with the original game and map selected. You can change either selection
before launching. Checks use the current promoted setup and latest game files,
and provisioning assigns a fresh lobby and port. The recorded files remain
visible as deployment history. Older deployments without a recorded recipe
retain their history but cannot offer this action.
## Promotions and deployment history
@@ -190,7 +199,7 @@ A preview shows the currently promoted managed files, configuration, and image
reference for the selected map. It does not pin those versions. New launches
resolve the promoted setup again when provisioning begins, so
promotions made after a preview or while a job is queued apply to that server.
This applies to collections, single-server launches, and **Launch again**.
This applies to collections, single-server launches, and **Launch another server**.
Previews and queued jobs store file metadata without copying script or plugin
contents for every lobby. Provisioning captures the bytes when each job starts.