Route definition in routes.rb in Ruby on Rails - Step-by-Step Execution

Concept Flow - Route definition in routes.rb

Start routes.rb file

↓

Define route method (get/post/etc)

↓

Specify URL path

↓

Map to controller#action

↓

Rails adds route to routing table

↓

Request matches route -> controller action called

↓

Response sent back to browser

This flow shows how Rails reads route definitions, adds them to its routing table, and uses them to direct web requests to the right controller actions.

Execution Sample

Ruby on Rails

get '/welcome', to: 'home#welcome'
post '/login', to: 'sessions#create'
root 'home#index'

Defines three routes: a GET route to welcome page, a POST route for login, and the root URL mapped to home#index.

Execution Table

Step	Route Method	URL Path	Controller#Action	Routing Table State
1	get	/welcome	home#welcome	Added GET /welcome -> home#welcome
2	post	/login	sessions#create	Added POST /login -> sessions#create
3	root	/	home#index	Added root / -> home#index
4	Request: GET /welcome	N/A	home#welcome	Matches GET /welcome route, calls home#welcome
5	Request: POST /login	N/A	sessions#create	Matches POST /login route, calls sessions#create
6	Request: GET /	N/A	home#index	Matches root route, calls home#index
7	Request: GET /unknown	N/A	No route	No matching route found, returns 404

💡 Routing stops when a matching route is found or returns 404 if none matches.

Variable Tracker

Routing Table	Start	After Step 1	After Step 2	After Step 3	Final
Routes	empty	GET /welcome -> home#welcome	GET /welcome -> home#welcome, POST /login -> sessions#create	GET /welcome -> home#welcome, POST /login -> sessions#create, root / -> home#index	GET /welcome, POST /login, root / routes defined

Key Moments - 3 Insights

Why does the root route use 'root' instead of get/post?

The root route is a special shortcut in Rails to define the home page URL ('/'). It always responds to GET requests. See execution_table row 3 where 'root' adds '/' route.

What happens if a request URL does not match any route?

Rails returns a 404 error because no route matches. This is shown in execution_table row 7 where GET /unknown has no matching route.

Can the same URL path have different routes for GET and POST?

Yes, GET and POST are different HTTP methods. Routes can differ by method even if URL path is same, as in rows 1 and 2.

Visual Quiz - 3 Questions

Look at the execution_table, what controller action is called for a GET request to '/welcome'?

A home#welcome

B sessions#create

C home#index

D No route

💡 Hint

Check execution_table row 4 for GET /welcome request.

At which step does the root route get added to the routing table?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at execution_table rows 1-3 for route additions.

If you send a POST request to '/welcome', what happens according to the execution_table?

A Calls home#welcome

B Returns 404 No route

C Calls sessions#create

D Calls home#index

💡 Hint

Check if POST /welcome route is defined in execution_table rows 1-3 and request matches in rows 4-7.

Concept Snapshot

Rails routes.rb defines URL paths and HTTP methods
Routes map to controller#action pairs
Use get/post/put/delete or root for home page
Rails builds routing table from these definitions
Requests match routes by method and path
No match returns 404 error

Full Transcript

In Rails, the routes.rb file defines how URLs connect to controller actions. Each route specifies an HTTP method like get or post, a URL path, and the controller and action to run. Rails reads these routes and builds a routing table. When a web request comes in, Rails looks up the routing table to find the matching route by method and path. If found, it calls the controller action. If no route matches, Rails returns a 404 error. The root route is a special shortcut for the home page URL '/'. This visual trace shows adding routes and how requests match them step-by-step.