Checking under the Hood: A guide to Rails Engines
summary
Rails 2.3 engines let a gem supply full MVC pieces — app/controllers, app/views, app/models — so reusable features can install routes, controllers and view templates; limitations include no migrations or public assets in the engine and the application’s paths win over engine files, so app paths override engine. Namespacing avoids class collisions. Engines can add rake tasks and require manual file copies for static files; example shipped is queso dynamic-search engine that marks a model searchable, provides UI and helper integration and works as a toy but needs manual asset and migration handling.
AI-written summary · about
chapters (18)
- 0:00Start
- 1:27Remember 2004?
- 1:58Rails Application?
- 2:23Remember 2006?
- 2:51Rails Plugins, then
- 3:35Rails Plugin, now
- 4:34Loading Rails...
- 4:53Remember 2009?
- 5:06Rails Engine (2009)
- 5:41Engines and MVC
- 6:34Models
- 8:10Controllers
- 8:43View
- 10:28Example init.rb
- 10:47Limitations
- 11:29Notable Engines
- 12:57Queso
- 14:38Conclusion
