docs: say what to back up, and why mydb.sqlite alone is not enough - #631
Open
spelingbee wants to merge 1 commit into
Open
docs: say what to back up, and why mydb.sqlite alone is not enough#631spelingbee wants to merge 1 commit into
spelingbee wants to merge 1 commit into
Conversation
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
spelingbee
force-pushed
the
docs-what-to-back-up
branch
from
September 4, 2026 09:40
976e3e5 to
144d10f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One paragraph under Deployment saying what to back up: the whole
datadirectory, becausemydb.sqliteon its own is missing the rows still in its-waland the files underuploads/andoutput/are not in the database at all. Tested on v0.18.0: restoringmydb.sqlitealone 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
datadirectory must be backed up, not justmydb.sqlite.mydb.sqlitealone is missing the-walfile with recent rows and theuploads/andoutput/files, so restoring only it leaves an instance that returns 403 at login.Written for commit 144d10f. Summary will update on new commits.