Host and exposure
Connect the workload to a realistic host capacity band and a deliberate public boundary instead of exposing every service by default.
Docker deployment planner
Turn a working Compose idea into an operating plan.
Define the workload, the host boundary, the data that must survive, and the public surface before a small deployment becomes an opaque collection of containers.
Start from a maintained workload
Three deployment paths worth maintaining deeply.
content site
WordPress public-site baseline
Keep the database and site files in one recoverable update point, then verify publishing, media, plugins, and public routing after change.
Open baseline →file sync
Nextcloud personal-cloud baseline
Keep files, database, configuration, custom apps, and themes synchronized through maintenance, upgrade, rollback, and client-facing restore checks.
Open baseline →source control
Gitea source-control baseline
Keep repositories, database, application data, configuration, and external object storage consistent through migration-aware update and clone/push recovery checks.
Open baseline →What this application owns
Deployment decisions before configuration sprawl.
State and recovery
Separate containers from the database, files, repositories, and configuration that have to be recovered together.