App folder organization in Ruby on Rails - Step-by-Step Execution

Concept Flow - App folder organization

Start: Rails app created

↓

Create app folder structure

↓

Add /app/controllers

↓

Add /app/models

↓

Add /app/views

↓

Add /app/helpers

↓

Add /app/assets

↓

Add /app/mailers

↓

Add /app/jobs

↓

Add /app/channels

↓

App folder ready for MVC and features

This flow shows how a Rails app organizes its main folders inside the app directory to separate concerns like controllers, models, views, and other features.

Execution Sample

Ruby on Rails

app/
  controllers/
  models/
  views/
  helpers/
  assets/

This shows the main folders inside the app directory of a Rails project, each serving a specific role.

Execution Table

Step	Folder Created	Purpose	Example Files
1	app/controllers	Handle user requests and responses	users_controller.rb, sessions_controller.rb
2	app/models	Manage data and business logic	user.rb, post.rb
3	app/views	Display HTML templates to users	users/index.html.erb, posts/show.html.erb
4	app/helpers	Provide methods to views for cleaner code	application_helper.rb
5	app/assets	Store images, stylesheets, and JavaScript files	stylesheets/application.css, javascripts/application.js
6	app/mailers	Send emails from the app	user_mailer.rb
7	app/jobs	Background tasks and asynchronous jobs	cleanup_job.rb
8	app/channels	WebSocket channels for real-time features	chat_channel.rb
9	End	All main app folders created	Ready for MVC and features

💡 All main app folders are created to organize code by responsibility.

Variable Tracker

Folder	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	After Step 7	After Step 8	Final
app/controllers	Not present	Created	Created	Created	Created	Created	Created	Created	Created	Created
app/models	Not present	Not present	Created	Created	Created	Created	Created	Created	Created	Created
app/views	Not present	Not present	Not present	Created	Created	Created	Created	Created	Created	Created
app/helpers	Not present	Not present	Not present	Not present	Created	Created	Created	Created	Created	Created
app/assets	Not present	Not present	Not present	Not present	Not present	Created	Created	Created	Created	Created
app/mailers	Not present	Not present	Not present	Not present	Not present	Not present	Created	Created	Created	Created
app/jobs	Not present	Not present	Not present	Not present	Not present	Not present	Not present	Created	Created	Created
app/channels	Not present	Not present	Not present	Not present	Not present	Not present	Not present	Not present	Created	Created

Key Moments - 3 Insights

Why do we have separate folders like controllers, models, and views?

Rails uses the MVC pattern to keep code organized. Controllers handle requests, models manage data, and views show the user interface. This separation makes the app easier to understand and maintain, as shown in steps 1-3 of the execution_table.

What is the purpose of the helpers folder?

Helpers contain methods that make views cleaner and easier to write. Instead of repeating code in views, helpers provide reusable functions. This is shown at step 4 in the execution_table.

Why are assets stored in a separate folder?

Assets like images, CSS, and JavaScript are kept in app/assets to separate static files from Ruby code. This helps Rails manage and serve these files efficiently, as seen in step 5.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the app/models folder created?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Check the 'Folder Created' column in execution_table row for step 2.

According to variable_tracker, which folder is created last?

A app/jobs

B app/mailers

C app/channels

D app/helpers

💡 Hint

Look at the last column 'Final' in variable_tracker to see which folder appears last.

If the app/helpers folder was missing, which step in execution_table would be skipped?

A Step 3

B Step 4

C Step 5

D Step 6

💡 Hint

Refer to the 'Folder Created' column in execution_table to find when helpers are created.

Concept Snapshot

Rails app folder organization:
- app/controllers: handle requests
- app/models: data and logic
- app/views: user interface
- app/helpers: view methods
- app/assets: static files
- Other folders: mailers, jobs, channels
Each folder keeps code clean and focused.

Full Transcript

This visual execution shows how a Rails app organizes its main folders inside the app directory. Starting from creating the controllers folder to handle user requests, then models for data, views for display, helpers for view methods, assets for static files, and other folders like mailers, jobs, and channels for specific features. Each step adds a folder with a clear purpose, helping keep the app organized and easy to maintain.

Practice

1. What is the main purpose of the app/ folder in a Rails application?

easy

A. To store database backups and logs

B. To hold static assets like images and stylesheets

C. To keep configuration files for the server

D. To organize the code by its role, like models, views, and controllers

Solution

1. Step 1: Understand the role of app/ folder

   The app/ folder is designed to organize the main parts of the Rails app code by their function.

2. Step 2: Identify what belongs in app/

   Models, views, and controllers are the core components stored in app/, not backups or static files.

3. Final Answer:

   To organize the code by its role, like models, views, and controllers -> Option D

4. Quick Check:

   App folder organizes code by role = B [OK]

Hint: Remember MVC parts live inside app/ folder [OK]

Common Mistakes:

• Confusing app/ with config/ or public/ folders
• Thinking assets like images go inside app/
• Assuming app/ holds database files

2. Which folder inside app/ should contain the code that responds to user requests?

easy

A. controllers

B. views

C. models

D. helpers

Solution

1. Step 1: Identify the role of controllers

   Controllers handle incoming user requests and decide what to do next.

2. Step 2: Match folder to role

   The controllers folder contains this code, while models manage data and views display content.

3. Final Answer:

   controllers -> Option A

4. Quick Check:

   Request handling = controllers = C [OK]

Hint: Controllers respond to requests inside app/ [OK]

Common Mistakes:

• Choosing models instead of controllers
• Confusing views with controllers
• Thinking helpers handle requests

3. Given this folder structure inside app/:
app/models/user.rb,
app/controllers/users_controller.rb,
app/views/users/index.html.erb
What is the role of users_controller.rb?

medium

A. It contains the HTML layout for user pages

B. It defines how user data is stored in the database

C. It manages the logic to handle user-related requests

D. It stores user session information

Solution

1. Step 1: Identify the controller file

   The file users_controller.rb is inside the controllers folder, so it handles requests.

2. Step 2: Understand controller responsibility

   Controllers manage logic for requests, not data storage or views.

3. Final Answer:

   It manages the logic to handle user-related requests -> Option C

4. Quick Check:

   Controller file handles requests = A [OK]

Hint: Controllers handle logic for requests, not data or views [OK]

Common Mistakes:

• Confusing controller with model responsibilities
• Thinking controller holds HTML templates
• Assuming controller stores session data

4. You accidentally put a view template file inside app/models/. What problem will this cause?

medium

A. The view will not render because Rails looks for templates only in app/views/

B. No problem; Rails loads views from any folder inside app/

C. The model will try to execute the view code causing a crash

D. Rails will raise an error because views must be in app/views/

Solution

1. Step 1: Understand Rails folder conventions

   Rails expects view templates only inside app/views/ to render them properly.

2. Step 2: Identify effect of wrong folder

   If a view is inside app/models/, Rails will not find it and won't render it.

3. Final Answer:

   The view will not render because Rails looks for templates only in app/views/ -> Option A

4. Quick Check:

   Views must be in app/views = D [OK]

Hint: Views only render from app/views folder [OK]

Common Mistakes:

• Expecting Rails to raise an error immediately
• Thinking models execute view code
• Assuming views load from anywhere in app/

5. You want to add a new feature that sends emails when a user signs up. Where should you place the mailer class in the Rails app/ folder structure?

hard

A. Inside app/controllers/ because it handles user actions

B. Inside app/mailers/ because mailers have their own folder

C. Inside app/models/ because it deals with user data

D. Inside app/views/ because emails have templates

Solution

1. Step 1: Recall Rails folder for mailers

   Rails has a dedicated app/mailers/ folder for mailer classes that send emails.

2. Step 2: Understand why mailers don't go elsewhere

   Controllers handle requests, models manage data, and views hold templates, but mailers have their own place.

3. Final Answer:

   Inside app/mailers/ because mailers have their own folder -> Option B

4. Quick Check:

   Mailers live in app/mailers = A [OK]

Hint: Put mailers in app/mailers folder [OK]

Common Mistakes:

• Placing mailers in controllers or models folders
• Confusing mailer classes with views
• Not knowing mailers have a separate folder