Marc-André Bombeck 1c10bbbde8 feat(admin): say per account how fresh the off-host copy is ...

The nightly off-host job reports counts — uploaded, failed, total — and a
count cannot name the account it is failing for. A cohort where one object
has been refused every night for a month reads as "99 uploaded, 1 failed"
each time, which looks like weather rather than like an account with no
disaster-recovery copy at all.

The worker now writes a ledger row when an object lands (account, instant,
size), and Admin → Backups gains a second card that rates every account
against the nightly schedule: fresh inside one run, due when one run
produced nothing, stale when two did not, never when no object has ever
landed. On a host without BACKUP_S3_* the card says off-host backup is not
configured and stops there.

The verdicts are computed from the ledger, never from a bucket listing: the
worker's grant is deliberately PutObject + GetObject, and an admin page must
not put the operator's credentials on its render path to state a number the
database already holds.

2026-09-10 09:27:58 +02:00

..

[section]

feat(admin): say per account how fresh the off-host copy is

2026-09-10 09:27:58 +02:00

page.tsx

fix(admin): replace hand-rolled read-error boxes with the shared primitive

2026-08-09 04:32:54 +02:00