How thurpe/recipes works
This is a Rails recipe-and-chef web application: visitors browse recipes, create or update recipes, like them, and register or manage chef profiles. Routes dispatch requests to controllers, which load or mutate domain records. The supplied excerpts document those controller actions and route mappings; model internals and views are not included, so persistence details are shown only at the model/database boundary.
Main entry points: routes.rb Routes · recipes_controller.rb Recipes controller · chef.rb Chef records · schema.rb Application database
Components 9
Web entry
- Routes
config/routes.rb - Pages controller
app/controllers/pages_controller.rb
Recipe activity
- Recipes controller
app/controllers/recipes_controller.rb
Chef profiles
- Chefs controller
app/controllers/chefs_controller.rb
Domain storage
- Recipe records
app/models/recipe.rb - Chef records
app/models/chef.rb - Like records
app/models/like.rb - Application database
db/schema.rb
Other components
- Visitor
Connections 11
- Visitor → Routes: sends request
- Routes → Pages controller: dispatches pages
- Routes → Recipes controller: dispatches recipes
- Routes → Chefs controller: dispatches chefs
- Recipes controller → Recipe records: finds and saves
- Recipes controller → Chef records: looks up chef
- Recipes controller → Like records: creates like
- Chefs controller → Chef records: finds and saves
- Recipe records → Application database: persists records
- Chef records → Application database: persists records
- Like records → Application database: persists records