Blueprint rules
Host band, exposure, state categories, and recovery checks are declared in domain logic and template metadata—not embedded in pages.
Methodology
Make the deployment logic inspectable.
The application combines transparent planning rules with upstream documentation. It distinguishes reusable deployment boundaries from configuration that must be verified for the exact image and application release.
Compose check
Pattern checks run locally in the browser. They identify review points; final Compose rendering and application testing remain part of deployment work.
Source review
Every maintained workload and guide declares relevant upstream source IDs and a review date.
Sources and scope
Last reviewed 2026-07-13. This page separates the decision it supports from the facts that still require a platform or model-specific check.
Applies to
The Docker deployment planner, Compose readiness check, maintained workload baselines, comparisons, and learning center.
Does not coverHands-on testing of every provider, app version, image tag, migration path, or operating environment.
Docker Compose production guidanceProduction-specific Compose configuration, restarts, ports, logging, and deployment changes.Open source ↗Docker Compose secrets guidanceExplicit secret access and file-backed secret patterns for Compose services.Open source ↗Docker Compose environment-variable guidanceEnvironment configuration and the distinction between variables and sensitive values.Open source ↗Docker Compose quickstartNamed volumes, environment configuration, and validating rendered Compose configuration.Open source ↗WordPress Docker Official Image documentationImage-specific environment, volume, and configuration information for the WordPress Docker Official Image.Open source ↗Nextcloud Docker image repositoryUpstream Docker image and Compose-related configuration material for Nextcloud.Open source ↗Gitea installation with DockerUpstream Docker and Compose installation guidance for Gitea.Open source ↗