Backups and upgrades for self-hosted Epure

This is the maintain checklist. If you need a vendor to own restores, wait for Cloud or stay on a managed rival.

Honesty limits

The upside is control. The work remains real. Software is Apache 2.0 at $0; you pay the VPS and your time.

Backup Postgres

• Identify the Postgres service/volume in your Compose file.
• pg_dump (custom or plain) to off-box storage on a schedule.
• Store dumps outside the VPS (object storage or another region).
• Quarterly: restore into a scratch Compose and confirm Issues UI still reads.

Exact dump flags depend on your Postgres 16 image; follow PostgreSQL docs. Do not invent Epure-specific dump wrappers here.

Upgrade images

• Read changelog / release notes for the Epure tag you want.
• Back up Postgres first.
• Pull new app (and Postgres only if intentional) tags.
• docker compose up -d with prod overlay.
• Watch /health and logs; send a Verify exception.

Sibling: Compose prod.

Rollback notes

Keep the previous app image tag and the dump from before the upgrade. Roll forward when migrations are one-way; restore from dump only if you tested that path.