Learning center
Learn only what changes the deployment.
Each guide connects a Compose decision to a practical operating boundary, with sources that can be revisited as Docker and upstream applications change.
deployment
Move a Docker Compose project to a single VPS
Plan the host boundary, public ports, persistent state, DNS, and recovery path before moving a Compose project from local testing to a public server.
Read guide →state
Map persistent Docker state before planning backups
Identify databases, files, repositories, attachments, and configuration that must be restored together after a Docker host incident.
Read guide →security
Plan public Docker ports and reverse-proxy boundaries
Keep public web access, internal application traffic, and database connectivity separated before exposing a Docker service.
Read guide →configuration
Separate Docker Compose configuration from sensitive values
Decide which Compose values are ordinary configuration and which need a narrower secret boundary before sharing or committing a project.
Read guide →operations
Plan Docker Compose updates and rollbacks before the first change
Turn image updates, database changes, and Compose edits into a repeatable operating procedure with a visible rollback point.
Read guide →