dorfteich/apps/backup/src/status.ts
Claude Fable 5 5cef359b8f
All checks were successful
CI / Lint, typecheck, test (push) Successful in 3m45s
CD / Build and push images (push) Successful in 3m49s
CI / Build container images (push) Has been skipped
CD / Deploy to Test (push) Successful in 9s
CD / Smoke tests against Test (push) Successful in 1m18s
CD / Promote to Int (push) Successful in 11s
CI / Auth e2e pack (push) Successful in 5m35s
CI / Import/export fidelity gate (push) Successful in 47s
Nextcloud backup target: admin-configured, manual + scheduled uploads, in-app restore (#103)
Off-host backups for every self-hoster, configured entirely in the admin
UI — supersedes the host-specific mirror plan behind #84.

shared:
- webdav.ts (new package entry like token-crypto): minimal WebDAV client
  with basic auth — PROPFIND (tolerant multistatus parser), MKCOL, PUT
  (streamed), GET, DELETE; Nextcloud DAV path derived from the plain
  server URL, explicit DAV bases pass through
- backup-status.ts: additive remote-upload status in status.json, the
  restore-status.json contract (running/succeeded/failed + staleness
  bound), the backup_command/backup_maintenance NOTIFY channels, and the
  one-bundle-per-set naming (dorfteich-backup-<id>.tar.gz)
- backup-set.ts moved here from apps/backup (api lists local sets)

backup sidecar:
- reads the backup.* instance settings directly from the database (admin
  changes apply next run; local retention row overrides the env) and the
  app password from the secret store
- after each successful set: bundle dump + files archive + manifest into
  ONE self-contained tar.gz, upload via WebDAV per schedule
  (off/daily/weekly; manual runs always upload), prune remote bundles —
  never the newest — and record the outcome in status.json; upload
  failures alert via a new backupUploadFailed mail (de+en)
- command listener on backup_command (run / restore) with a serial queue
  against the nightly timer
- restore orchestrator: restore-status.json → maintenance NOTIFY →
  grace → (remote: download + manifest-verify bundle) → terminate other
  DB connections → shared perform-restore path (same code as restore.sh)
  → final status + maintenance exit

api:
- MaintenanceGuard (global, registered before the setup gate): 503
  maintenance_mode while restore-status says running; health endpoints
  and the new public GET /backup/restore-status stay exempt; a stale
  running state (crashed sidecar) unblocks after 30 min
- MaintenanceStateService watches the file and restarts the api after a
  successful restore (fresh caches, migrate-on-start for older dumps);
  main.ts refuses to touch the database while a restore runs — a
  container restarting mid-restore must not race pg_restore with
  migrate deploy
- worker sweeps (conversion, mail outbox, scheduler) catch transient
  database failures instead of dying on an unhandled rejection — the
  restore's connection termination crashed the api in verification
- backup admin endpoints under /admin/system/backup: settings (live
  connection test before save, password write-only into the secret
  store), nextcloud/test, sets (local via the ro backups mount + remote
  via WebDAV), run + restore (type-to-confirm backstop, source
  validation) — commands travel as NOTIFY payloads; audit actions
  backup.settings_changed/run_triggered/restore_requested
- readyz: new warning-level backup_remote check while a target is
  configured (26 h daily / 170 h weekly bound)

collab:
- maintenance listener: on enter, persist + close every live session and
  refuse new connections until exit (failsafe timeout 30 min) — no
  in-memory document may write pre-restore content back afterwards

web:
- Admin → System backup section: status card with remote facts and a
  "Back up now" button, the Nextcloud settings form with test button,
  and the restore picker (local + remote sets, type-to-confirm)
- global maintenance screen: any 503 maintenance_mode flips the SPA to a
  status page polling the exempt endpoint, reloading when the instance
  returns

Verified end-to-end against a live stack (fresh DB, native api + sidecar,
fake WebDAV server): configure → test → manual backup → bundle upload →
readyz/sets/status surfaces → remote restore with maintenance gate,
marker rollback and api restart; suites: shared 21, backup 9, collab 11,
api 58 files green, lint + i18n:check + typecheck clean.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EwZ4jR4KFAPvpjWevfUGX1
2026-07-12 10:39:18 +02:00

58 lines
2.0 KiB
TypeScript

import { existsSync, readFileSync } from 'node:fs';
import { rename, writeFile } from 'node:fs/promises';
import { join } from 'node:path';
import {
BACKUP_STATUS_FILE,
RESTORE_STATUS_FILE,
type BackupStatus,
type RestoreStatus,
} from '@dorfteich/shared';
/**
* File I/O for `status.json` on the backups volume. The shape itself is a
* shared contract (`@dorfteich/shared` backup-status.ts) because the api's
* readiness check (#85) and admin panel (#86) read what this sidecar writes.
*/
export type { BackupRun, BackupSizes, BackupStatus } from '@dorfteich/shared';
export { BACKUP_STATUS_FILE as STATUS_FILE } from '@dorfteich/shared';
/** Reads the previous status; a missing or torn file is simply "no status". */
export function readStatus(backupsDir: string): BackupStatus | null {
const path = join(backupsDir, BACKUP_STATUS_FILE);
if (!existsSync(path)) return null;
try {
return JSON.parse(readFileSync(path, 'utf8')) as BackupStatus;
} catch {
return null;
}
}
/** Atomic write (staging + rename) so readers never see a torn file. */
export async function writeStatus(backupsDir: string, status: BackupStatus): Promise<void> {
await writeJsonAtomic(join(backupsDir, BACKUP_STATUS_FILE), status);
}
/** The in-app restore progress file (issue #103) — same contract discipline
* as status.json: the api's maintenance gate and admin card read it. */
export function readRestoreStatus(backupsDir: string): RestoreStatus | null {
const path = join(backupsDir, RESTORE_STATUS_FILE);
if (!existsSync(path)) return null;
try {
return JSON.parse(readFileSync(path, 'utf8')) as RestoreStatus;
} catch {
return null;
}
}
export async function writeRestoreStatus(backupsDir: string, status: RestoreStatus): Promise<void> {
await writeJsonAtomic(join(backupsDir, RESTORE_STATUS_FILE), status);
}
async function writeJsonAtomic(path: string, value: unknown): Promise<void> {
const staging = `${path}.tmp-${process.pid}`;
await writeFile(staging, JSON.stringify(value, null, 2) + '\n');
await rename(staging, path);
}