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.

Practice

1. What does the root route do in a Rails application?

easy

A. It specifies the layout template for all pages.

B. It defines a new database table for the app.

C. It creates a new controller automatically.

D. It sets the default page visitors see at the website's base URL.

Solution

1. Step 1: Understand the purpose of root route

   The root route defines what page loads when someone visits the main URL of the website.

2. Step 2: Identify what root route sets

   It sets the default controller action to show, so visitors see a starting page without errors.

3. Final Answer:

   It sets the default page visitors see at the website's base URL. -> Option D

4. Quick Check:

   Root route = default homepage [OK]

Hint: Root route sets homepage URL view [OK]

Common Mistakes:

• Confusing root route with database or controller creation
• Thinking root route sets layout or styles
• Assuming root route is optional for homepage

2. Which of the following is the correct syntax to set the root route to the home action in the pages controller?

easy

A. root 'pages#home'

B. root to: 'pages#home'

C. root pages#home

D. root => 'pages#home'

Solution

1. Step 1: Recall root route syntax

   The standard syntax is root 'controller#action' without extra keywords.

2. Step 2: Check each option

   root 'pages#home' matches the correct syntax exactly. root to: 'pages#home' adds unnecessary to:, C misses quotes, D uses old hash rocket syntax incorrectly.

3. Final Answer:

   root 'pages#home' -> Option A

4. Quick Check:

   Syntax = root 'controller#action' [OK]

Hint: Use quotes and # between controller and action [OK]

Common Mistakes:

• Adding extra keywords like 'to:' incorrectly
• Omitting quotes around controller#action
• Using old hash rocket syntax in modern Rails

3. Given this routes file snippet:

Rails.application.routes.draw do
  root 'welcome#index'
  get 'about', to: 'pages#about'
end

What happens when a user visits http://localhost:3000/?

medium

A. The browser redirects to /about automatically.

B. The pages#about action runs and its view is shown.

C. The welcome#index action runs and its view is shown.

D. A routing error occurs because root is not set.

Solution

1. Step 1: Identify root route action

   The root route is set to welcome#index, so visiting '/' triggers this action.

2. Step 2: Understand other routes

   The /about path goes to pages#about, but it is not the root URL.

3. Final Answer:

   The welcome#index action runs and its view is shown. -> Option C

4. Quick Check:

   Root URL = welcome#index [OK]

Hint: Root route controls '/' URL behavior [OK]

Common Mistakes:

• Confusing root route with other get routes
• Expecting automatic redirects without code
• Assuming missing root causes errors

4. You wrote this in config/routes.rb:

root 'main#home'
root 'dashboard#index'

What is the problem with this code?

medium

A. The syntax is wrong; root needs a block, not a string.

B. You cannot define more than one root route; it causes a conflict.

C. The controller names must be capitalized.

D. This code will work fine and set the root to the last line.

Solution

1. Step 1: Check root route rules

   Rails allows only one root route. Defining multiple causes conflicts or errors.

2. Step 2: Analyze given code

   Two root routes are defined, which is invalid and will cause routing errors.

3. Final Answer:

   You cannot define more than one root route; it causes a conflict. -> Option B

4. Quick Check:

   Only one root route allowed [OK]

Hint: Only one root route per app allowed [OK]

Common Mistakes:

• Thinking last root route overrides previous silently
• Confusing root route syntax with controller naming
• Believing multiple root routes are valid

5. You want your Rails app to show the landing page from the home controller as the root route, but only if the user is not logged in. Otherwise, it should show dashboard#index. How can you set this up?

hard

A. Set root to a controller action that redirects based on login status.

B. Define two root routes with conditions in routes.rb.

C. Use root 'home#landing' and add a before_action in dashboard.

D. Set root to dashboard#index and ignore login status.

Solution

1. Step 1: Understand root route limitation

   Rails allows only one root route, so conditional logic must be inside the controller.

2. Step 2: Implement conditional redirect

   Set root to a controller action (e.g., home#root_redirect) that checks login and redirects accordingly.

3. Final Answer:

   Set root to a controller action that redirects based on login status. -> Option A

4. Quick Check:

   Use controller logic for conditional root [OK]

Hint: Use controller action to redirect root conditionally [OK]

Common Mistakes:

• Trying to set multiple root routes with conditions
• Ignoring login status in root route setup
• Assuming routes.rb supports conditional root directly