Feature/192 backup directories #193

2026-08-26T10:57:21-05:00

bermudalamb commented

2026-08-26 10:57:21 -05:00

No description provided.

bermudalamb self-assigned this 2026-08-26 10:57:21 -05:00

bermudalamb added this to the Code Quality and Hardening 2 project 2026-08-26 10:57:21 -05:00

bermudalamb added 2 commits 2026-08-26 10:57:22 -05:00

docs(ops): say that the backup directories have to be created (#192 ) 724e9ce19d

The stack gained two backup services in #147 and nothing has ever told anyone to create the directories they mount. `backup-and-restore.md` reads from both paths and the compose file mounts both, but no document creates them — while the README does exactly that for QA's data directories, ownership notes and all. Production's cutover runbook said nothing.

Hit for real during the cutover: both backup containers sat in Created, never started, and `docker logs` on them reported only that nothing matched the filter, because a container that never ran has no output. Portainer showed them beside the healthy ones and the stack looked deployed.

That silence is the reason this is worth a step of its own rather than a footnote. A backup regime that never started is indistinguishable from a working one until someone needs a restore, which is the failure mode the healthchecks in #147 exist to catch — and those healthchecks cannot fire on a container that is not running.

The cutover runbook gains the directory creation before the stack is created, and step 7 now counts containers rather than only checking the app: four, all Up, with Created called out as the thing to look for. Counted from the compose file rather than from memory — the first draft said five.

`backup-and-restore.md` gains the same note where it describes the destinations, since anyone reading that page is already thinking about paths.

No `chown`, deliberately stated: both backup images run as root, unlike the Postgres image whose data directory needs uid 999, and an unnecessary chown instruction is how people learn to run them without thinking.

docs(ops): prove the backups during the cutover rather than waiting for a schedule (#192 )

SonarQube Analysis / sonarqube (pull_request) Failing after 30m13s

Details

Linting / lint (pull_request) Successful in 2m45s

Details

1a59edec18

Step 4b created the directories and step 7 checked the containers were Up. Neither established that a restorable file actually gets written, and those are not the same claim — the database backup does not run until 03:00 and the uploads archive not until Sunday 04:00, so a stack that looks correct at the end of a cutover can be four days from its first evidence.

Both tools take a manual trigger, so the wait is unnecessary. The runbook now forces one run of each, checks the sizes are plausible, and greps the dump for `COPY` lines on the real tables — a dump of an empty database succeeds and looks fine, which is the one way this check could otherwise lie.

It also confirms the healthchecks agree with where the files landed. A check whose `find` path disagrees with where the tool actually writes reports unhealthy forever while the backups are working perfectly, and that is a thing to discover on the day the stack is built rather than a year later.

`starting` corrected to `unhealthy` in the surrounding text: during `start_period` Docker reports `starting`, which is what an operator actually sees and what the previous wording got wrong.

Proven against production during the cutover on 2026-08-26 — a 41K dump and a 15M archive, both landing where the healthchecks look.

bermudalamb merged commit fdb5b7a0be into main

2026-08-26 10:58:15 -05:00

bermudalamb deleted branch feature/192-backup-directories

2026-08-26 10:58:23 -05:00

bermudalamb moved this to Review in Code Quality and Hardening 2 on 2026-08-27 11:09:16 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: bermudalamb/redefined-designs#193