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>
62 lines
2.1 KiB
SQL
62 lines
2.1 KiB
SQL
-- Minstrel's own backup: its settings and its runs.
|
|
|
|
-- name: GetBackupSettings :one
|
|
SELECT * FROM backup_settings WHERE id = true;
|
|
|
|
-- name: SaveBackupSettings :exec
|
|
UPDATE backup_settings
|
|
SET enabled = $1,
|
|
destination = $2,
|
|
folder = $3,
|
|
endpoint = $4,
|
|
bucket = $5,
|
|
access_key = $6,
|
|
secret_key = $7,
|
|
run_hour = $8,
|
|
upload_limit_kib = $9,
|
|
updated_at = now()
|
|
WHERE id = true;
|
|
|
|
-- name: StartBackupRun :one
|
|
INSERT INTO backup_runs (trigger) VALUES ($1)
|
|
RETURNING id, started_at;
|
|
|
|
-- name: FinishBackupRun :exec
|
|
UPDATE backup_runs
|
|
SET status = $2,
|
|
finished_at = now(),
|
|
location = $3,
|
|
bytes = $4,
|
|
error = $5
|
|
WHERE id = $1;
|
|
|
|
-- name: ListBackupRuns :many
|
|
SELECT id, trigger, status, started_at, finished_at, location, bytes, error
|
|
FROM backup_runs
|
|
ORDER BY started_at DESC
|
|
LIMIT $1;
|
|
|
|
-- name: BackupRunTimes :one
|
|
-- The times the verdict turns on. A run that never happened is the epoch,
|
|
-- so the row always exists. failing_since is the first failure after the last
|
|
-- success, and the epoch when the latest finished run succeeded.
|
|
SELECT
|
|
COALESCE((SELECT max(started_at) FROM backup_runs WHERE status = 'succeeded'),
|
|
'epoch'::timestamptz)::timestamptz AS last_success,
|
|
COALESCE((SELECT max(started_at) FROM backup_runs),
|
|
'epoch'::timestamptz)::timestamptz AS last_attempt,
|
|
COALESCE((SELECT min(started_at) FROM backup_runs
|
|
WHERE status = 'failed'
|
|
AND started_at > COALESCE((SELECT max(started_at) FROM backup_runs WHERE status = 'succeeded'),
|
|
'epoch'::timestamptz)),
|
|
'epoch'::timestamptz)::timestamptz AS failing_since;
|
|
|
|
-- name: FailUnfinishedBackupRuns :execrows
|
|
UPDATE backup_runs
|
|
SET status = 'failed', finished_at = now(),
|
|
error = 'The server stopped while the backup was running.'
|
|
WHERE status = 'running';
|
|
|
|
-- name: PruneBackupRuns :execrows
|
|
DELETE FROM backup_runs WHERE status <> 'running' AND started_at < $1;
|