fix: narrow backup scope to database and telegram sessions

This commit is contained in:
2026-07-22 09:31:07 +02:00
parent 3536089d52
commit 03822e0763
10 changed files with 174 additions and 186 deletions
+8 -5
View File
@@ -142,11 +142,14 @@ docker compose --profile bot up -d
### Production Backups
Docker volumes are not backups. Production backups protect PostgreSQL, durable
STL uploads, and the worker and bot Telegram session volumes in an encrypted
Restic repository on a Synology NFS share. See the [backup and recovery
guide](scripts/backup/README.md) for Synology setup, secrets, systemd
installation, monitoring, retention, and guarded restore procedures.
Docker volumes are not backups. Production backups protect a PostgreSQL
logical dump plus the worker and bot Telegram session volumes in an encrypted
Restic repository on a Synology NFS share. `manual_uploads` and temporary ZIP
processing data are excluded; STL binaries remain in Telegram, while the
database mappings and Telegram IDs are what recovery preserves for lookup and
delivery. See the [backup and recovery guide](scripts/backup/README.md) for
Synology setup, secrets, systemd installation, monitoring, retention, and
guarded restore procedures.
### Seeding the Database