Change operations

Plan Docker Compose updates and rollbacks before the first change

An update plan is a recovery plan with a smaller time window and a clearer definition of success.

Record the deployed state

Keep the rendered Compose configuration, image versions, environment references, and the state backup associated with the current deployment. This gives an update a known point to return to.

Change one meaningful layer at a time

Avoid combining host changes, proxy changes, database migrations, and application upgrades in one unreviewed operation. Keep the operation small enough that a failed check identifies the layer that changed.

Render the deployed and proposed models with the same project inputs, then compare service additions and removals, image references, ports, environment keys, persistent mounts, permissions, networks, health checks, dependencies, restart behavior, and log limits. Values behind environment keys remain outside the exported change plan.

Verify the restored service, not only the container

After an update or rollback, test the user-facing service and the state it depends on. A running container does not prove that data, jobs, routes, or credentials are correct.