fix: use absolute /data path for SQLite in .env.example to match Docker volume#139
Merged
nullure merged 1 commit intoCaviraOSS:mainfrom Feb 24, 2026
Merged
Conversation
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
2 participants
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.
Closes #135
The
.env.examplesetsOM_DB_PATH=./data/openmemory.sqlite(relative path), but the Docker volume indocker-compose.ymlis mounted at/data. When users copy.env.exampleto.env, the SQLite file is created at./data/inside the container (not on the mounted volume), causing all data to be lost on container restart.This fix changes the example path to
/data/openmemory.sqlite(absolute) to match the volume mount point.