Advanced / user manual
Deployments and Preview Deployments
Runs rolling, blue-green, and preview delivery flows. Records digest-pinned revisions with gated steps, one active deployment per server, per-PR preview environments, and separate zero-downtime releases.
Coordinate deployments, traffic, scaling, security, and provider integrations.
Rollout flow
One active deployment per server
How to use it
Operator workflow
- 01
Trigger a rollout with a digest-pinned image and health gate.
- 02
Follow gated steps; only one deployment runs per server.
- 03
Compare revisions and roll back to a completed target when needed.
- 04
Use preview environments per pull request with TTLs for pre-merge verification.
What Forge owns
Boundary and safety
Rollback mirrors a recreate deployment against a completed target — never the live one.
Review the affected node, workload, route, or secret before saving. Capture state and health evidence before changes that affect data or public traffic.
Before you finish
Verification checklist
- Deployment reaches completed.
- Revision recorded with config hash.
- Rollback row written on revert.
- Preview closes and cleans up.
Continue the manual
Use this feature in the wider Forge workflow.
Move from platform understanding to the relevant operating guide when you need exact environment, network, deployment, or recovery steps.