Method
A simple method, applied first to our own platform.
Principles
- Everything is in git. Configuration files, deployment definitions and documentation are versioned. An installation can be rebuilt identically, and every change leaves a trace.
- No secrets in the code. Passwords and keys live in environment variables or dedicated files, outside the repositories.
- One step at a time. Each change is verified before the next, with a rollback plan.
- Backups get tested. A backup that has never been restored is not a backup: we verify and rehearse restores.
- Document to hand over. Installation, maintenance and disaster-recovery procedures, written to be followed without their author.
A concrete example
Our own platform applies these principles: services in Docker containers, a Traefik reverse proxy with automatic Let's Encrypt certificates, deployments driven by Komodo from GitLab, encrypted backups pulled every night to another server, and monitoring of availability and certificates.
Scoping a project
Before starting, we write down together what is included, what is not, the risks identified and how to roll back. The quote follows from this scoping.