Add single database configuration instructions #37
Conversation
This file contains 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
npezza93
requested changes
Sep 23, 2024
Co-authored-by: Nick Pezza <[email protected]>
Co-authored-by: Nick Pezza <[email protected]>
npezza93
approved these changes
Sep 24, 2024
rnestler
reviewed
Feb 3, 2025
| Running Solid Cable in a separate database is recommended, but it's also possible to use a single database for both the app and Action Cable. | ||
|
|
||
| 1. Copy the contents of `db/cable_schema.rb` into a normal migration and delete `db/cable_schema.rb` | ||
| 2. Remove `connects_to` from `config/cable.yml` |
There was a problem hiding this comment.
Shouldn't we still have a connects_to (just pointing to primary) to ensure that it uses a separate DB connection?
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.
I'm running a super simple application that used Sidekiq and Redis. I replaced that with Solid Queue and Solid Cable. However, because the application is super slim I don't think I need to separate the queue and cable into their own databases. I found the instructions for doing so in the Solid Queue repository but couldn't find it for Solid Cable.