Backups & Upgrades
What to back up
| Data | Where | Backed up automatically? |
|---|---|---|
| Database (users, tasks, conversations, settings) | /data/meowbert/postgres-data | Yes, as weekly dumps in /data/meowbert/postgres-backups |
| Project and task files | /srv/meowbert/runtime | No |
| Cold task history, if enabled | The archive mount and archivesDir configured under taskHistoryArchive | No |
| Your configuration | config/global.docker.json, .env | No |
The postgres-backup service writes a compressed pg_dump every Sunday at midnight and keeps two weeks by default. Change the schedule and retention in .env (MEOWBERT_POSTGRES_BACKUP_SCHEDULE, MEOWBERT_POSTGRES_BACKUP_KEEP_WEEKS, …).
For a complete backup, copy the database dumps, /srv/meowbert/runtime, any separate cold-history archive, and your config files to another machine or storage with your usual tool, such as restic, borg, or rsync.
Cold storage moves message bodies, media, and execution history out of PostgreSQL. A database dump keeps their identities and archive references, but cannot recover those payloads without the archive files. Keep the archive and database backups together, including any older single-file archives retained during conversion.
Restoring the database
gunzip -c /data/meowbert/postgres-backups/last/<backup>.sql.gz \
| docker compose exec -T meowbert-postgres psql -U postgres -d meowbertRestore into an empty database, before starting the API and worker. Restore the project files and matching cold-history archive too, and make its configured mount available to both services before starting them.
Upgrading
git pull
docker compose pull sandbox-runtime
docker compose up -d --buildIf you run the full stack with email, add -f docker-compose.full.yml to both docker compose commands.
Database migrations run automatically when the API starts. Check the changelog before upgrading for anything that needs your attention.