feat(backup): dump Uptime Kuma before each backup #6

Merged
jonnxor merged 1 commit from jonnxor/feat/backup-kuma into main 2026-10-31 16:36:35 +00:00 AGit
Owner

Backs up Uptime Kuma, whose monitors and notifications exist only in a SQLite database in a Podman volume. It follows Forgejo's pattern.

  • dump_kuma takes a consistent copy with SQLite's .backup and writes ~/Backups/uptime-kuma/uptime-kuma-dump.tar, owner-readable only because it holds notification tokens and the admin password hash. A failed dump keeps the last good one and doesn't stop the backup.
  • include.txt covers the new path, and verify gains a check that the dump is readable and contains kuma.db.
  • docs/recovery.md has the restore steps.

Tested on hades, on scratch paths only: the dump, the failure and not-running cases, and a restore into a throwaway instance (admin account back, integrity check ok, app redirects to the dashboard).

Not tested: a full mise run backup or backup:verify through restic. Those need this merged and a real run.

Timing: the monthly verify runs on 2026-11-01 around 09:46, after the nightly backup around 03:05. Merge and pull before the backup, or after verify. In between, verify fails and raises a false alarm because the snapshot has no Kuma dump yet.

🤖 Generated with Claude Code

Backs up Uptime Kuma, whose monitors and notifications exist only in a SQLite database in a Podman volume. It follows Forgejo's pattern. - `dump_kuma` takes a consistent copy with SQLite's `.backup` and writes `~/Backups/uptime-kuma/uptime-kuma-dump.tar`, owner-readable only because it holds notification tokens and the admin password hash. A failed dump keeps the last good one and doesn't stop the backup. - `include.txt` covers the new path, and `verify` gains a check that the dump is readable and contains `kuma.db`. - `docs/recovery.md` has the restore steps. **Tested on hades, on scratch paths only:** the dump, the failure and not-running cases, and a restore into a throwaway instance (admin account back, integrity check ok, app redirects to the dashboard). **Not tested:** a full `mise run backup` or `backup:verify` through restic. Those need this merged and a real run. **Timing:** the monthly verify runs on 2026-11-01 around 09:46, after the nightly backup around 03:05. Merge and pull before the backup, or after verify. In between, verify fails and raises a false alarm because the snapshot has no Kuma dump yet. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(backup): dump Uptime Kuma before each backup
All checks were successful
CI / sanity (pull_request) Successful in 6s
fd25dc4cf1
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
WAAAGH/_workdesk!6
No description provided.