Root route in Ruby on Rails - Step-by-Step Execution

Concept Flow - Root route

Start Rails app

↓

Check routes.rb

↓

Find root route

↓

Map '/' URL to controller#action

↓

User visits '/'

↓

Rails sends request to mapped controller action

↓

Controller renders view

↓

User sees homepage

Rails looks at the root route in routes.rb to decide what controller action to run when the user visits the home page URL '/'

Execution Sample

Ruby on Rails

Rails.application.routes.draw do
  root 'home#index'
end

This code sets the root URL '/' to run the index action in the HomeController

Execution Table

Step	Action	Input	Result	Notes
1	Start Rails server	N/A	Server running	Rails app boots and loads routes
2	Read routes.rb	routes.rb file	Find root 'home#index'	Root route is set
3	User visits '/' URL	GET /	Request received	Browser sends request to root URL
4	Rails matches route	Request path '/'	Matches root route	Rails finds root route mapping
5	Call controller action	home#index	HomeController#index runs	Controller action executes
6	Render view	index.html.erb	HTML page generated	View template renders
7	Send response	HTML content	Browser displays homepage	User sees homepage content
8	End	N/A	Request complete	Cycle finished

💡 Request completes after rendering the root route's controller action and view

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 5	Final
root_route	undefined	'home#index'	'home#index'	'home#index'	'home#index'
request_path	N/A	N/A	'/'	'/'	'/'
controller_action	N/A	N/A	N/A	HomeController#index	HomeController#index
response_content	N/A	N/A	N/A	N/A	Rendered homepage HTML

Key Moments - 3 Insights

Why does Rails need a root route defined?

Rails uses the root route to know which controller action to run when the user visits the home page URL '/'. Without it, visiting '/' would cause an error. See execution_table step 4 where Rails matches the root route.

What does 'root "home#index"' mean in routes.rb?

It means the root URL '/' will run the index action inside the HomeController. This is shown in execution_table step 5 where the controller action is called.

What happens if the user visits a URL other than '/'?

Rails looks for a matching route for that URL. If no route matches, it returns a 404 error. The root route only handles the '/' URL as shown in execution_table step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what controller action runs when the user visits '/'?

A ApplicationController#show

B RootController#home

C HomeController#index

D No action runs

💡 Hint

Check step 5 in the execution_table where the controller action is called

At which step does Rails match the root route to the request path '/'?

A Step 2

B Step 4

C Step 6

D Step 7

💡 Hint

Look at the 'Action' and 'Result' columns in execution_table step 4

If the root route was not defined, what would happen when visiting '/'?

A Rails would return a 404 error

B Rails would redirect to '/home'

C Rails would use a default controller

D Rails would crash

💡 Hint

Refer to key_moments about why root route is needed and what happens if missing

Concept Snapshot

Root route in Rails sets the homepage URL '/'.
Syntax: root 'controller#action'
When user visits '/', Rails runs that controller action.
Without root route, '/' causes error.
Defined in config/routes.rb.
Maps URL to controller#action for homepage.

Full Transcript

In Rails, the root route defines what happens when a user visits the home page URL '/'. The root route is set in the config/routes.rb file using the syntax root 'controller#action'. When the Rails server starts, it reads this file and stores the root route mapping. When a user visits '/', Rails matches this URL to the root route and calls the specified controller action. That action runs and renders a view, which is sent back as HTML to the browser. This process ensures the user sees the homepage content. If the root route is not defined, visiting '/' will cause an error because Rails does not know which controller action to run. This visual trace showed each step from server start, reading routes, receiving the request, matching the root route, running the controller, rendering the view, and sending the response.