Repository navigation
Retire the idle Action Cable stack - #33
Merged
Merged
Conversation
Nothing in the app subscribes or broadcasts: there is no turbo_stream_from, no broadcast call and no channel, and the only Turbo in use is the request/response turbo_stream templates. Yet every boot loaded the Action Cable engine, mounted /cable, and kept a fourth SQLite database for solid_cable. This removes the solid_cable gem, the action_cable/engine require, config/cable.yml, the production cable database and its schema. turbo-rails runs without Action Cable on its own. The file already on the production volume is left alone: nothing opens it any more, and Litestream never replicated it. To bring it back, re-add the solid_cable gem, the action_cable/engine require, config/cable.yml, db/cable_schema.rb and the production cable database. Keep a database-backed adapter: the likely first subscriber is a refresh pushed to an open iPad when an operation run from a console or runner process changes a child's day, and only the database crosses that process boundary.
6temes
changed the title
6temes
marked this pull request as ready for review
October 1, 2026 06:44
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
1 participant
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.
Nothing in deures broadcasts or subscribes, yet every boot loaded the Action Cable engine, mounted
/cable, and kept a fourth SQLite database for solid_cable. Production now runs on three databases (primary, cache, queue) and serves no/cableendpoint. Pages, answer submissions and the system tests are unchanged, since the only Turbo in use is request/responseturbo_streamtemplates.The five places cable lived are all gone:
gem "solid_cable",require "action_cable/engine",config/cable.yml, the productioncable:database inconfig/database.yml, anddb/cable_schema.rb. turbo-rails runs without Action Cable on its own.bin/rails routesnever listed/cable: Action Cable mounts it as an internal route, which that command hides. The check that the endpoint is gone therefore reads the route table directly. It printedtrueonmainand printsfalseon this branch, in both development and production.The cable file already on the production volume is left in place on purpose. Nothing opens it any more, and Litestream never replicated it. The commit message records how to bring the stack back, for when a realtime feature needs it.
Nothing a person sees changes, so there are no screenshots.
Session-settled decisions carried from planning: retire the stack in one commit (user-approved, over keeping the idle stack).