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
+4 -3
View File
@@ -41,9 +41,9 @@ export type KnownEnv = {
* their own keys beside these for bots and computers to use.
*
* Not here, and never in the `envs` table: `ENCRYPTION_KEY` and
* `ENCRYPTION_SALT` (they encrypt the table), and `PORT`, `DATA_DIR` and
* `MAIN_SERVER` (the container's own start-up settings). Those stay in the
* process environment.
* `ENCRYPTION_SALT` (they encrypt the table), and `PORT`, `DATA_DIR`,
* `BACKUP_ARCHIVE_DIR` and `MAIN_SERVER` (the container's own start-up
* settings). Those stay in the process environment.
*/
export const EnvDict: readonly KnownEnv[] = [
{
@@ -95,6 +95,7 @@ export const ProcessOnlyEnvKeys = [
"PORT",
"DATA_DIR",
"DB_DIR",
"BACKUP_ARCHIVE_DIR",
"MAIN_SERVER",
] as const;
-1
View File
@@ -34,7 +34,6 @@ export type SettingsPage = {
export const SettingsComputersPath = "/admin/settings/computers";
export const SettingsBackupsPath = "/admin/settings/backups";
export const SettingsBackupsRestorePath = `${SettingsBackupsPath}/restore`;
/**
* The `/admin/settings/*` sub pages, listed in the rail on every settings