Advanced / user manual
Compose
Imports and manages Compose files. Validates security-sensitive directives server-side, runs live stacks with GitOps (poll, preview, drift, rollback), and keeps legacy projects and per-app compose views separate.
Coordinate deployments, traffic, scaling, security, and provider integrations.
Compose intake flow
Stacks are live; projects are store-only
How to use it
Operator workflow
- 01
Validate the document server-side before creating anything.
- 02
Create a stack on a node with resources and env.
- 03
Deploy, stop, restart, and read logs per stack.
- 04
Attach GitOps for branch tracking, previews, drift, and webhooks — or keep projects as store-only documents.
What Forge owns
Boundary and safety
Stacks, projects, and per-app compose views are three separate models with separate endpoints.
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
- Validation passes with no security errors.
- Stack status reaches running.
- Logs stream per service.
- Drift check clean or explained.
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.