Skip to content

docs: say what to back up, and why mydb.sqlite alone is not enough - #631

Open
spelingbee wants to merge 1 commit into
C4illin:mainfrom
spelingbee:docs-what-to-back-up
Open

docs: say what to back up, and why mydb.sqlite alone is not enough#631
spelingbee wants to merge 1 commit into
C4illin:mainfrom
spelingbee:docs-what-to-back-up

Conversation

@spelingbee

@spelingbee spelingbee commented Sep 4, 2026

Copy link
Copy Markdown

One paragraph under Deployment saying what to back up: the whole data directory, because mydb.sqlite on its own is missing the rows still in its -wal and the files under uploads/ and output/ are not in the database at all. Tested on v0.18.0: restoring mydb.sqlite alone gives an instance that answers 403 at login; restoring the directory restores everything.

Closes #630.


Summary by cubic

Adds backup guidance to the README explaining that the whole data directory must be backed up, not just mydb.sqlite.

Written for commit 144d10f. Summary will update on new commits.

Review in cubic

@github-actions github-actions Bot added the Docs label Sep 4, 2026
One paragraph under Deployment saying what to back up: the whole `data` directory, because `mydb.sqlite` on its own is missing the rows still in its `-wal` and the files under `uploads/` and `output/` are not in the database at all. Tested on v0.18.0: restoring `mydb.sqlite` alone gives an instance that answers 403 at login; restoring the directory restores everything.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0193orVXP78niTTs6AzLThHK
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: a line on what to back up - mydb.sqlite alone restores an instance you cannot log in to

2 participants