Use current promoted files for blueprint launches
This commit is contained in:
@@ -116,10 +116,15 @@ 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.
|
||||
Blueprints save maps and target lobby counts. Every new server uses the latest
|
||||
promoted scripts, plugins, and configuration when provisioning begins, including
|
||||
promotions made after preview or while queued. Existing blueprints automatically
|
||||
follow this policy. Deployment history records the files selected for that launch;
|
||||
**Launch again** uses the current promoted setup for the same game and map.
|
||||
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,
|
||||
reproducibility boundaries, and API details.
|
||||
promotion policy, and API details.
|
||||
|
||||
## Saved server keys
|
||||
|
||||
|
||||
Reference in New Issue
Block a user