Ruby on Rack: The Magic Between Request and Response
summary
Claims that Rack is a tiny, composable API that actually bridges servers and frameworks and lets plain Ruby handle real features are proven by code and a working demo: a TIL app built with Sequel + Postgres, Slim templates, static assets and a file-backed counter; custom Rack middleware for URL rewriting and a rate limiter that issues 429s after ten posts per minute and enforces a six‑second cooldown; real‑time updates via Faye::WebSocket successfully broadcast to multiple browsers.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 1:04From curiosity to Ruby on Rack
- 5:14TIL Rack app demo
- 7:03What Rack is
- 7:45Rack’s minimal API
- 9:51Rack and web servers
- 11:39Rack’s server abstractions
- 13:30Rack request handling
- 15:39Rack in web frameworks
- 16:01Sinatra’s Rack integration
- 16:43Middleman’s middleware
- 17:25Rails’ Rack init
- 18:06Composing with middleware
- 18:27Custom Rack middleware
- 19:30TIL app with Rack
- 19:51First commit setup
- 20:53Slim templates
- 21:59Static assets middleware
- 22:42Dynamic routes
- 23:04Sequel database
- 24:07Rack routing
- 25:31TILs display
- 26:40File persistence
- 27:43Real-time JS
- 28:26Rate limiting
- 31:59WebSocket support
- 35:11Extending possibilities
- 35:54Why learn Rack
- 36:14Middleware next steps
- 36:57Closing
