feat: Minstrel backs itself up nightly to a folder or an S3 bucket, off until an admin switches it on (#6773)
release / web (push) Failing after 15s
release / govulncheck (push) Successful in 16s
release / go (push) Failing after 41s
release / integration (push) Failing after 3m29s
release / android (push) Successful in 4m7s
release / Attach APK to the Release (tag releases only) (push) Canceled after 0s
release / Build + push container image (push) Canceled after 0s
release / Verify release artifacts (tag releases only) (push) Canceled after 0s
release / Build signed APK (push) Canceled after 5m34s

Admin › Backups shows a verdict first (off, not set up, waiting, backed up,
overdue, failing since when), Back up now, Test destination and the latest
runs, with the settings beside them.

- backup.Service: one run at a time, bounded at 30 minutes; the schedule
  ticks every 5 minutes, catches up a slot missed while the server was down,
  and retries a failure after an hour and then after as long as it has been
  failing. Runs are recorded in backup_runs, pruned after 90 days; a run cut
  off by a shutdown is marked failed at the next start.
- A folder destination writes database/minstrel-<UTC stamp>.tar and refuses
  a folder that isn't there. An S3 destination stages the file, hashes it,
  and uploads it under database/ through a throttled reader (4 MiB/s by
  default, 0 for no limit).
- Test destination checks the form as typed and only lists.
- The bucket secret is sealed like every stored credential; backup_settings
  and backup_runs are left out of the backup itself.
- The panel polls only while a run is going, capped at the run limit plus
  five minutes.

The music switch named in the task is left to #6774, so no control ships
that does nothing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-02 14:50:55 -05:00
co-authored by Claude Opus 5.5
parent faf19ef67b
commit 9d324ab2d0
29 changed files with 2384 additions and 4 deletions
@@ -0,0 +1,2 @@
DROP TABLE IF EXISTS backup_runs;
DROP TABLE IF EXISTS backup_settings;
@@ -0,0 +1,44 @@
-- 0099_backups.up.sql — Minstrel backing itself up.
--
-- backup_settings one row: whether the nightly backup is on, where it goes
-- (a folder, or an S3 bucket such as a Fabled Archives
-- target), and the hour it runs, in UTC. Off until an
-- admin switches it on.
-- backup_runs one row per attempt: when, what started it, how it ended,
-- where the file went, its size, and the error in words.
CREATE TABLE backup_settings (
id boolean PRIMARY KEY DEFAULT true CONSTRAINT backup_settings_one_row CHECK (id),
enabled boolean NOT NULL DEFAULT false,
destination text NOT NULL DEFAULT 's3'
CONSTRAINT backup_settings_destination_check CHECK (destination IN ('folder', 's3')),
folder text NOT NULL DEFAULT '',
endpoint text NOT NULL DEFAULT '',
bucket text NOT NULL DEFAULT '',
access_key text NOT NULL DEFAULT '',
-- Sealed under the stream secret, as every stored credential is.
secret_key text NOT NULL DEFAULT '',
run_hour smallint NOT NULL DEFAULT 3
CONSTRAINT backup_settings_run_hour_check CHECK (run_hour BETWEEN 0 AND 23),
-- The most an upload to the bucket may send, in KiB a second; 0 is no limit.
upload_limit_kib integer NOT NULL DEFAULT 4096
CONSTRAINT backup_settings_upload_limit_check CHECK (upload_limit_kib >= 0),
updated_at timestamptz NOT NULL DEFAULT now()
);
INSERT INTO backup_settings DEFAULT VALUES;
CREATE TABLE backup_runs (
id uuid PRIMARY KEY DEFAULT gen_random_uuid(),
trigger text NOT NULL
CONSTRAINT backup_runs_trigger_check CHECK (trigger IN ('schedule', 'manual')),
status text NOT NULL DEFAULT 'running'
CONSTRAINT backup_runs_status_check CHECK (status IN ('running', 'succeeded', 'failed')),
started_at timestamptz NOT NULL DEFAULT now(),
finished_at timestamptz,
-- Where the file went: the object key, or the file's path in the folder.
location text NOT NULL DEFAULT '',
bytes bigint NOT NULL DEFAULT 0,
error text NOT NULL DEFAULT ''
);
CREATE INDEX backup_runs_started_at_idx ON backup_runs (started_at DESC);