mirror of
https://github.com/xCyanGrizzly/DragonsStash.git
synced 2026-09-21 13:31:42 +00:00
fix: narrow backup scope to database and telegram sessions
This commit is contained in:
@@ -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
|
||||
|
||||
|
||||
Reference in New Issue
Block a user