Backup and restore

All data lives in one folder: ./pb_data next to docker-compose.yml — the SQLite database plus uploaded files. Nothing of yours is stored anywhere else, and nothing is stored inside the container.

The bundled script

./backup.sh                 # creates kb-backup-YYYY-MM-DD.tgz
./backup.sh restore FILE    # restores data from a backup

By hand

Back up by copying the pb_data folder; restore by putting it back. That is genuinely all there is to it.

docker compose down
tar czf kb-backup-$(date +%F).tgz pb_data
docker compose up -d

Take one before a bigger update

Database migrations run automatically on start, and they run forward only. A backup taken before docker compose up -d --build is the difference between a bad afternoon and a bad week.

Verify the backup, do not assume it

A backup you have never restored is a hypothesis. Restore it once into a throwaway copy:

mkdir /tmp/kb-restore-test && cd /tmp/kb-restore-test
tar xzf /path/to/kb-backup-2026-07-30.tgz
ls pb_data          # you should see data.db and a storage folder

What is not in the backup

.env and docker-compose.override.yml are your configuration, not data — the script does not include them. Keep them somewhere too; without them a restored instance comes up with default ports, no AI, and no Google sign-in.