fix: Revert back to single SQLite connection by default - #7346
Merged
Conversation
)" This reverts commit ba85804.
louislam
changed the title
UPTIME_KUMA_SQLITE_SINGLE_CONNECTION"
Closed
2 tasks
Contributor
There was a problem hiding this comment.
Pull request overview
Reverts the previously added SQLite single-connection toggle, returning SQLite pooling behavior to a fixed configuration in the backend database initialization (server/database.js).
Changes:
- Removes support for
UPTIME_KUMA_SQLITE_SINGLE_CONNECTION. - Inlines the SQLite pool configuration directly in the knex config (
min: 0,max: 20) without conditional overrides.
1 task
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.
Reverts #7312
avoid unnecessary back and forth