feat(backup): dump Uptime Kuma before each backup #6
Loading…
Reference in a new issue
No description provided.
Delete branch "jonnxor/feat/backup-kuma"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Backs up Uptime Kuma, whose monitors and notifications exist only in a SQLite database in a Podman volume. It follows Forgejo's pattern.
dump_kumatakes a consistent copy with SQLite's.backupand 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.txtcovers the new path, andverifygains a check that the dump is readable and containskuma.db.docs/recovery.mdhas 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 backuporbackup:verifythrough 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