Deployment Patterns 🟢

Patterns shared across all RMM self-hosted deployments.

Canonical shape

Internet ──▶ nginx (TLS + rate limits) ──▶ Docker Compose services ──▶ Postgres/Redis/Qdrant

Naming & versions

• Deploy from git tags, never from branch tips.
• Pin image versions in compose; :latest is forbidden in production.
• One directory per stack: docker-compose.yml + .env.example + README.md.

Zero-downtime upgrades

1. Pull tag, build image alongside running container (docker compose build).
2. Run migrations (idempotent, expand/contract pattern).
3. Recreate services one at a time behind the proxy (docker compose up -d --no-deps <svc>).
4. Smoke-test health endpoints; roll back by re-pointing compose to previous tag.

Backups

Data	Cadence	Retention
Postgres	Nightly dump + weekly restore test	30 days local, 90 days offsite
Redis	RDB snapshot (cache data — rebuildable)	7 days
Qdrant	Snapshot weekly	4 weeks
Secrets store	Encrypted export weekly	offsite

Restore tests are mandatory weekly. An untested backup is a hope, not a backup.