Switch configuration storage from .env to SQLite (breaking change) #540
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.
Summary
This PR replaces the current .env-based configuration with a SQLite-backed config store.
SQLite was chosen for simplicity, zero external dependencies, and to enable editing configuration while the container is running via the existing web interface at /admin.
Breaking change
This is an intentional breaking change:
The goal is to avoid dual config sources and long-term maintenance complexity.
Notes / limitations
Compatibility path
If this approach is considered too disruptive, the implementation can be refactored to:
That was intentionally deferred to keep this PR focused unless required.
Scope
This PR is limited to configuration storage changes only. No unrelated behavior or features are introduced.