Skip to content

Activate Solid Cable for production Action Cable#3535

Open
Rolling2405 wants to merge 3 commits intoDARIAEngineering:mainfrom
Rolling2405:feature/activate-solid-cable
Open

Activate Solid Cable for production Action Cable#3535
Rolling2405 wants to merge 3 commits intoDARIAEngineering:mainfrom
Rolling2405:feature/activate-solid-cable

Conversation

@Rolling2405
Copy link
Copy Markdown
Contributor

@Rolling2405 Rolling2405 commented Apr 8, 2026

I rule and have completed some work on Case Manager that's ready for review!

This activates Solid Cable as the Action Cable adapter in production, enabling real-time WebSocket features (like live notifications) to work without needing a separate Redis server.

This pull request makes the following changes:

  • Configure Action Cable to use the Solid Cable adapter in production
  • Solid Cable was already in the Gemfile — this activates it

For reviewer:

  • Adjust the title to explain what it does for the notification email to the listserv.
  • Tag this PR:
    • feature if it contains a feature, fix, or similar. This is anything that contains a user-facing fix in some way, such as frontend changes, alterations to backend behavior, or bug fixes.
    • dependencies if it contains library upgrades or similar. This is anything that upgrades any dependency, such as a Gemfile update or npm package upgrade.
  • If it contains neither, no need to tag this PR.

Rolling2405 and others added 3 commits April 7, 2026 18:16
Re-enable solid_cable adapter in cable.yml for production.
Schema (cable_schema.rb) already exists. Replaces async adapter
which only works within a single process.

Polling interval: 0.1s, message retention: 1 day.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Creates lib/tasks/solid.rake with a 'solid:setup' task that:
- Creates and migrates Solid Cache, Cable, and Queue databases
- Handles pre-existing databases gracefully (skips creation)
- Falls back to loading schema files if no migrations exist
- Reconnects to primary database after setup
- Works across all Rails environments

Note: This file is duplicated on feature/activate-solid-cache. When
merging, whichever PR merges second will have no merge conflict since
the file content is identical.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Change 'rescue => e' to 'rescue StandardError => e' in solid.rake
to avoid catching non-standard exceptions like SignalException.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant