Archive the whole data volume in Backups, not just the database

Settings > Backups gains a whole-data archive beside the database
snapshots, and both lists now fully work from the page.

- Data archives: `write-data-backup-archive.ts` tars all of DATA_DIR into
  BACKUP_ARCHIVE_DIR as cobble-data-<epoch-ms>.tar.gz, every entry under one
  root folder named after the archive, writing a .part name and renaming on
  success so a cut-off run is never listed. The newest
  AppData.DataBackupsKept are kept; db/.backups is left as it is.
- Restore: `restore-data-backup.ts` extracts to a temp dir, requires one
  root folder holding a db folder, takes a safety archive first, then
  replaces DATA_DIR (the database snapshots included) and `restart-app.ts`
  restarts the process through the docker socket, since the open SQLite
  handle points at the replaced file.
- Upload and restore: a modal over each list (database file or data
  archive), replacing the old /admin/settings/backups/restore page.
- Delete for both kinds, icon-only row actions shared through
  RowIconButton, and restore on every row.
- One backup or restore of either kind at a time (with-backup-run-lock).
- BACKUP_ARCHIVE_DIR is a start-up path (ProcessOnlyEnvKeys); the installer
  mounts $COBBLE_HOME/backups-archives at /backups-archives and recreates a
  container that lacks it. The image installs tar and gzip.
This commit is contained in:
2026-10-22 11:00:37 +01:00
parent fd75111bb1
commit a88898d169
56 changed files with 1686 additions and 261 deletions
+7 -3
View File
@@ -70,6 +70,10 @@ Before the first public release:
- Images are tagged with the release version, so an older tag can be
installed with `--version vX.Y.Z`.
- The installer keeps the last five database backups in
`$COBBLE_HOME/backups`.
- Restore a backup from **Settings > Backups** in the app, or restore the
files with the app stopped.
`$COBBLE_HOME/backups`. Whole-data archives from Settings > Backups live
in `$COBBLE_HOME/backups-archives`; they are kept, not pruned by the
installer.
- Restore a backup from **Settings > Backups** in the app: a database
snapshot, or a whole-data archive (which replaces every folder, the
snapshots included, takes a safety archive first and restarts the app).
A snapshot can also be restored with the app stopped.