Skip to content

Remove Redis and the Rails.cache layer#619

Merged
fwuensche merged 1 commit into
mainfrom
fwuensche/check-redis-usage
Apr 20, 2026
Merged

Remove Redis and the Rails.cache layer#619
fwuensche merged 1 commit into
mainfrom
fwuensche/check-redis-usage

Conversation

@fwuensche

Copy link
Copy Markdown
Contributor

Summary

  • Removes the redis, hiredis, and connection_pool gems so the Heroku Redis add-on can be destroyed after merge.
  • Deletes the two Rails.cache.fetch call sites (Metric#chart_data, Api::MetricsController#index) — the 12h TTL wasn't worth the infra given chart data invalidates on every push and the API cache actually returned stale metric data to the CLI.
  • Switches the ActionCable production adapter from redis to async (there were no channels, broadcasts, or subscriptions).
  • package-lock.json churn is unrelated npm peer-dep metadata reshuffling already present in the workspace.

Test plan

  • CI green (full test suite — local run hit an unrelated pg gem segfault on macOS)
  • After merge: heroku addons:destroy heroku-redis --app cherrypush-production and heroku config:unset REDIS_URL

🤖 Generated with Claude Code

Drops the Redis dependency entirely so the Heroku Redis add-on can be removed.
ActionCable was configured on Redis but had no channels, broadcasts, or
subscriptions. The two Rails.cache call sites (Metric#chart_data and
Api::MetricsController#index) had 12h TTLs on data that either invalidates on
every push or returns stale values for the CLI API — not worth the infra.
@fwuensche fwuensche merged commit c92b925 into main Apr 20, 2026
2 checks passed
@fwuensche fwuensche deleted the fwuensche/check-redis-usage branch April 20, 2026 12:23
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