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
A content-site deployment path with database state, uploaded media, HTTPS, backups, and update checks.
Build the baseline →file sync
Nextcloud personal-cloud baseline
A file-sync deployment path with file data, database state, background work, HTTPS, and off-server recovery checks.
Build the baseline →source control
Gitea source-control baseline
A Git-service deployment path with repositories, attachments, database state, SSH exposure, and restore checks.
Build the 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.