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
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
68 lines
2.5 KiB
TypeScript
68 lines
2.5 KiB
TypeScript
import { execFile } from 'node:child_process';
|
|
import { existsSync } from 'node:fs';
|
|
import { basename, dirname } from 'node:path';
|
|
import { promisify } from 'node:util';
|
|
|
|
const execFileAsync = promisify(execFile);
|
|
|
|
/**
|
|
* The uploads and plugins directories travel in one tar archive per restore
|
|
* set (ADR 0015). Both must share a parent directory (in the compose stack
|
|
* that is `/data`): entries are stored relative to it (`uploads/…`,
|
|
* `plugins/…`), so extraction lands exactly where the api reads.
|
|
*/
|
|
export function archiveBase(dataDirs: string[]): { base: string; names: string[] } {
|
|
const bases = new Set(dataDirs.map((dir) => dirname(dir)));
|
|
if (bases.size !== 1) {
|
|
throw new Error(
|
|
`data directories must share one parent to form a single archive, got: ${dataDirs.join(', ')}`,
|
|
);
|
|
}
|
|
return { base: [...bases][0]!, names: dataDirs.map((dir) => basename(dir)) };
|
|
}
|
|
|
|
async function runTar(args: string[]): Promise<void> {
|
|
try {
|
|
await execFileAsync('tar', args, { maxBuffer: 16 * 1024 * 1024 });
|
|
} catch (error) {
|
|
const stderr = (error as { stderr?: string }).stderr?.trim();
|
|
throw new Error(`tar failed: ${stderr || (error as Error).message}`);
|
|
}
|
|
}
|
|
|
|
/** Creates the gzip'd volume archive; directories that do not exist yet
|
|
* (fresh instance without uploads) are skipped, an empty set still produces
|
|
* a valid empty archive. */
|
|
export async function createArchive(outFile: string, dataDirs: string[]): Promise<void> {
|
|
const { base, names } = archiveBase(dataDirs);
|
|
const existing = names.filter((name) => existsSync(`${base}/${name}`));
|
|
if (existing.length === 0) {
|
|
await runTar(['-czf', outFile, '--files-from', '/dev/null']);
|
|
return;
|
|
}
|
|
await runTar(['-czf', outFile, '-C', base, ...existing]);
|
|
}
|
|
|
|
/** Unpacks a volume archive back over the data directories (restore path). */
|
|
export async function extractArchive(archiveFile: string, dataDirs: string[]): Promise<void> {
|
|
const { base } = archiveBase(dataDirs);
|
|
await extractArchiveTo(archiveFile, base);
|
|
}
|
|
|
|
/** Unpacks any of our tar.gz archives into a destination directory. */
|
|
export async function extractArchiveTo(archiveFile: string, destDir: string): Promise<void> {
|
|
await runTar(['-xzf', archiveFile, '-C', destDir]);
|
|
}
|
|
|
|
/**
|
|
* Packs individual files (relative to `baseDir`, stored flat) into a gzip'd
|
|
* tar — the remote bundle format of issue #103.
|
|
*/
|
|
export async function createArchiveOfFiles(
|
|
outFile: string,
|
|
baseDir: string,
|
|
fileNames: string[],
|
|
): Promise<void> {
|
|
await runTar(['-czf', outFile, '-C', baseDir, ...fileNames]);
|
|
}
|