Conversation
|
I guess we need to analyze how this conflicts with the |
|
@brunoprietog Good point. Think we can maybe just use the inline adapter there. |
* main: Add Solid Cable (#52889) Fix syntax error in user.rb
* main: Skip solid_cable gem if skip_action_cable is set (#52919) Call prerecord in test parallelization Fix a documentation name mismatch in cookies.rb Revert "Assign id attributes first in Active Record attribute assignment" Do not populate CurrentAttributes#attributes when not using defaults Suppress a RuboCop offense after running `rails new` with `--devcontainer` Fix small typo for Solid Cable changelog [ci skip] (#52911) Use less queries when updating nested attributes Load routes in LazyRoutesSet#recognize_path Slim down the gem section for Solid Add Solid Cable (#52889) Fix syntax error in user.rb Improve Active Record Association Callbacks docs [ci skip] Assign id attributes first in Active Record attribute assignment Always separate config blocks with a CR Fixup tests for #52850 Replace "healthcheck" with "health check" in documentation. [ci-skip]
* Add Solid Cable Co-authored-by: Nick Pezza <pezza@hey.com>
|
Normally, when I need to reflect changes after executing a job or service, and I'm using Turbo Streams to make the application truly live, I utilize Redis even in development. This allows me to open the console, jobs, execute commands, and see the changes reflected in the open connections (the users interacting with the application). However, if I switch to inline jobs, will that consume more memory? @dhh |
Solid Cable is the last piece before we can fully claim that Rails 8 only requires a database as a dependency to get access to all frameworks and functionality. Thanks to @npezza93 for the great work!