Add multi-server blueprint collections and atomic launches
This commit is contained in:
@@ -70,10 +70,13 @@ the sweep marks pending rows `manual` so nothing hangs forever.
|
||||
|
||||
## Deployment blueprints and launch previews
|
||||
|
||||
Deployments now includes a blueprint library and a two-step launch composer.
|
||||
Preview a promoted game/map setup, save its managed files as a reusable blueprint,
|
||||
or launch again from a recorded deployment. Previews check configuration and
|
||||
available capacity; every queued creation retains its own launch recipe.
|
||||
Deployments includes a blueprint builder for whole server collections: choose
|
||||
multiple T5/T6 maps, set a lobby count for each, and launch the lineup in one action.
|
||||
The collection preview shows every server ID, port, and saved-key requirement.
|
||||
All jobs and capacity reservations are committed together before provisioning;
|
||||
one collection page tracks each server's independent progress and failures.
|
||||
Existing single-server blueprints can be expanded with **Edit**. Single-server
|
||||
launches and launching again from recorded recipes remain available.
|
||||
The progress page explains waiting conditions, shows elapsed time, and can resume
|
||||
health verification of an interrupted creation when its original server remains.
|
||||
See [Deployment blueprints](docs/deployment-blueprints.md) for the workflow,
|
||||
|
||||
Reference in New Issue
Block a user