Compose configuration
Compare the rendered stack with the deployment you planned.
Carry the workload boundary from the blueprint, parse the final application model locally, then export one launch checklist for exposure, persistent state, recovery, and runtime controls.
Compose preflight
Inspect the rendered application model against one explicit deployment boundary.
Compare published ports, persistent mounts, sensitive-value paths, privileges, lifecycle controls, and recovery work with the blueprint that led here.
The deployment context in the URL contains only workload, host, exposure, recovery priority, and protected-state size. Pasted Compose content stays in this browser and is never added to the URL or saved plan history.
Attached deployment blueprint
—
—
—
Generic inspection
No deployment blueprint is attached.
The structural analysis still runs, while exposure and recovery remain confirmation items until an intended boundary is attached.
Build and attach a blueprintCheck result
Paste a Compose configuration to begin.
Persistent-state map
Connect each state-bearing service to a mount and a recovery action.
Launch checklist
Separate completed configuration checks from work that still needs proof.
Editorial record
Maintained by Make Your Own Tools to turn “Validate a deployment” into a defined host, state, exposure, and recovery boundary. The references below provide the technical context for this planning path. Its calculation rules and planning assumptions are documented in the methodology, and affected calculations pass regression checks before the review date advances.
- Last reviewed
- Evidence set
- 7 primary references