Add single database configuration section #276
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
Similar to solid_queue, this documents how to configure Solid Cache to use a single database instead of separate databases for the app and cache.
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.
Ref: rails/solid_queue#334
This adds a "Single database configuration" section to the README, similar to what exists in solid_queue. While running Solid Cache in a separate database is recommended for production use, this documentation helps users who want to use a single database for simplicity or in development environments.
FWIW I'd advocate for
rails newto default to using a single database for the Solid stuff, but I think that ship has already sailed... ⛵ 👋 🤣