Extending Rails 3

on YouTube ↗29m

" summary

Rails 3.1 makes concrete changes: engine migrations get a copy-and-timestamp workflow so gems ship migrations safely; the static middleware uses a pre-populated hash for fast multi-public-directory serving; isolated engines become mountable Rack apps with their own routers and app/assets; SCSS/Coffee compile is a template handler and assets go to app/assets; HTTP caching ships as rack-cache tied to whatever Rails.cache uses; streaming uses chunked encoding with optional auto-flush and known exception caveats.

AI-written summary · about

" chapters (12)

1. 0:00Start
2. 1:12Extending Rails 3
3. 3:26Static Assets (without copying)
4. 4:58Self-Contained Engine
5. 9:39Hardcoded File System & Nginx/Apache
6. 9:50Read-Only File System
7. 10:25Built-in HTTP Caching
8. 15:51Enables Edge-Cached SCSS
9. 17:41compilation golden pipeline
10. 19:40engines get app/assets
11. 21:57Conventional Usage
12. 23:52caveats

" related talks

• 38mRails 3.1 Whirlwind TourBen Scheirman · LoneStarRuby Conf 2011
• 59mRailsConf 2011, David Heinemeier HanssonDavid Heinemeier Hansson · RailsConf 2011
• 48mFrom Rails to Rack: Making Rails 3 a Better Ruby CitizenYehuda Katz · GoRuCo 2009
• 01h 09mRails 3 ...and the real secret to high productivityDavid Heinemeier Hansson · RailsConf 2009
• 37mCreating Mountable EnginesPatrick Peak · RailsConf 2013
• 22mChecking under the Hood: A guide to Rails EnginesMike Perham · Lone Star Ruby Conference 2009
• 35mChanging the wheels on the bus at 80 mph: Upgrading to Rails 3Andrew Bloomgarden, Julian Giuca · RailsConf 2013
• 39mThe Long Ball - Upgrading long lived Rails apps from 1.x-4.0Jesse Wolgamott · RailsConf 2013