ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Turbo Streams let Rails push small HTML fragments over Action Cable to update part of a page — no custom JavaScript. A worked comment-thread example, plus the trade-offs and how to verify it.
Turbo Streams declaratively updates page regions via server-rendered HTML, enabling live Rails features without JavaScript. This post covers the concept, a concrete comment-feed example, and trade-offs to watch.
Rails 7’s Hotwire lets you build real‑time, interactive apps with minimal JavaScript. This guide walks through setting up Turbo Streams and Stimulus, shows a live‑update task list, and weighs Hotwire’s trade‑offs versus heavy front‑end frameworks.
An architecture note on using Turbo Streams for live Rails page updates: the minimal three-piece design, trust and authorization boundaries, operational checks, and the failure modes that would push you toward a client state layer.
Turbo Streams let servers push real‑time DOM updates over WebSocket or SSE, keeping the browser in sync without full reloads. Learn how to set up a Rails 7 chat example, weigh trade‑offs, and get started quickly.
Goal We want to display a large list of records in a Rails view using Reflex to update the list via Turbo Streams, while limiting the number of records per page and preserving the current page across multiple Reflex invocations. Constraints Reflex actions are stateless between requests; ActiveRecord scopes can bound a query with limit and offset , but the cl
Goal Determine whether a Turbo Streams WebSocket connection remains open or automatically reconnects when the server detects that a user’s authentication has expired or been revoked. Constraints Least‑privilege enforcement relies on server‑side middleware; the stream endpoint must reject messages from unauthenticated or unauthorized users. When a session tok
rails
turbo
reflex