ActionCable for Not-Another-Chat-App-Please
summary
Rails 5 ActionCable brings WebSockets into Rails with concrete claims: use cookies.signed user_id for auth (no session), call action_cable.server.broadcast from controllers, jobs or models, and render partials outside requests via application_controller.render for server-generated HTML. Examples built and working: cart sync across tabs, slide presenter with client→server perform methods, per-job UUID streams for async tasks, and Trello-style collaboration. Deployment options: in-process async for single server, Redis pub/sub for multiple dynos, standalone server for scale; beta3 ships Feb 2016.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:32F5 Refresh
- 5:45Web Sockets
- 13:42First ActionCable Beta
- 18:16Channel
- 21:30Subscription
- 24:17Data Updates
- 28:26JavaScript Hooks
- 31:38Collaboration
- 32:35Asynchronous Tasks
- 34:59Deployment - Standalone
- 36:40Gotchas
related talks
34mUnraveling the Cable: How ActionCable works
28mReal-time collaboration with Rails
37mUntangling cables and demystifying twisted transistors
38mAnycable - Universal Action Cable
47mActionCable, Rails API and React - Modern Single Page Apps
23mImplications of the Realtime Web
36mThe pitfalls of realtime-ification
35mThe Action Cable Symphony - An Illustrated Musical Adventure