Laravel project structure - Step-by-Step Execution

Concept Flow - Laravel project structure

Start Laravel Project

↓

Create folders: app, bootstrap, config, database, public, resources, routes, storage, tests

↓

Add files in folders: Controllers, Models, Views, Config files, Routes files

↓

Load environment settings (.env)

↓

Bootstrap framework (load service providers, middleware)

↓

Run application (handle requests, send responses)

↓

Log and cache data in storage

↓

End

This flow shows how Laravel organizes its project folders and files, loads settings, prepares the framework, and runs the app.

Execution Sample

Laravel

app/
bootstrap/
config/
database/
public/
routes/

These are main folders created in a Laravel project to organize code, configs, and public files.

Execution Table

Step	Action	Folder/File Created or Loaded	Purpose
1	Create main folders	app, bootstrap, config, database, public, resources, routes, storage, tests	Organize code, configs, assets, and tests
2	Add subfolders and files	app/Models, app/Http/Controllers, resources/views, routes/web.php	Separate models, controllers, views, and routes
3	Load environment file	.env	Load environment variables like DB credentials
4	Bootstrap framework	bootstrap/app.php	Initialize Laravel core and service providers
5	Load config files	config/*.php	Load app settings like database, cache, mail
6	Handle HTTP request	public/index.php	Entry point to process web requests
7	Run middleware and route	app/Http/Middleware, routes/web.php	Process request and find matching route
8	Execute controller	app/Http/Controllers/*	Run business logic and prepare response
9	Render view	resources/views/*.blade.php	Generate HTML response
10	Store logs and cache	storage/logs, storage/framework/cache	Save logs and cache data
11	Send response	HTTP response	Return output to browser
12	End	-	Request cycle complete

💡 Request handled and response sent, Laravel cycle ends

Variable Tracker

Folder/File	Created/Loaded	Purpose
app/	Created	Holds application code like models and controllers
bootstrap/	Created	Loads framework and service providers
config/	Created	Stores configuration files
database/	Created	Contains migrations and seeds
public/	Created	Public web root with index.php
resources/	Created	Views, language files, and assets
routes/	Created	Route definitions
storage/	Created	Logs, cache, and compiled files
.env	Loaded	Environment variables for app settings

Key Moments - 3 Insights

Why is the public folder important in Laravel?

The public folder contains index.php, the entry point for all web requests, and public assets. It is the only folder exposed to the web server, protecting other files.

What is the role of the routes folder?

The routes folder holds files like web.php that define URL paths and link them to controllers. This controls how requests are handled.

Why do we have separate folders like app, config, and resources?

Separating code (app), settings (config), and views/assets (resources) helps keep the project organized and easier to maintain.

Visual Quiz - 3 Questions

Look at the execution table, which step loads the environment variables?

A Step 6

B Step 5

C Step 3

D Step 1

💡 Hint

Check the 'Folder/File Created or Loaded' column for '.env' in the execution table

At which step does Laravel handle the HTTP request?

A Step 4

B Step 6

C Step 9

D Step 2

💡 Hint

Look for 'Handle HTTP request' action in the execution table

If the public folder was missing, what would happen?

A The app would fail to receive web requests

B Controllers would not execute

C Laravel would not load environment variables

D Views would not render

💡 Hint

Refer to key moment about the public folder and step 6 in the execution table

Concept Snapshot

Laravel Project Structure:
- app/: application code (models, controllers)
- bootstrap/: framework bootstrap files
- config/: configuration files
- database/: migrations and seeds
- public/: web root, contains index.php
- resources/: views and assets
- routes/: route definitions
- storage/: logs and cache
- .env: environment settings
Request flow: public/index.php -> routes -> controller -> view -> response

Full Transcript

Laravel projects have a clear folder structure to organize code and resources. The main folders include app for code, bootstrap for framework setup, config for settings, database for migrations, public as the web root, resources for views and assets, routes for URL definitions, and storage for logs and cache. The .env file holds environment variables like database credentials. When a web request comes in, it hits public/index.php, which boots Laravel, loads configs and environment variables, runs middleware, finds the matching route, executes the controller, renders the view, and sends the response back to the browser. This organized flow helps keep Laravel projects clean and maintainable.

Practice

1. Which folder in a Laravel project contains the files that define the URL routes for the application?

easy

A. config

B. app

C. resources

D. routes

Solution

1. Step 1: Understand the purpose of the routes folder

   The routes folder holds files that define how URLs map to code actions in Laravel.

2. Step 2: Compare with other folders

   The app folder contains core code, resources holds views and assets, and config stores configuration settings.

3. Final Answer:

   routes -> Option D

4. Quick Check:

   URL routes = routes folder [OK]

Hint: Routes are always in the routes folder [OK]

Common Mistakes:

• Confusing app with routes folder
• Thinking views are in routes
• Mixing config files with routes

2. Which of the following is the correct path to store Blade template files in a Laravel project?

easy

A. public/templates

B. app/Views

C. resources/views

D. config/views

Solution

1. Step 1: Identify where Blade templates are stored

   Blade templates are stored in the resources/views folder by Laravel convention.

2. Step 2: Verify other options

   app/Views is not standard, public/templates is for public assets, and config/views is not used for templates.

3. Final Answer:

   resources/views -> Option C

4. Quick Check:

   Blade templates = resources/views [OK]

Hint: Templates live in resources/views folder [OK]

Common Mistakes:

• Putting templates in app folder
• Confusing public assets with views
• Trying to store views in config folder

3. Given this Laravel project structure snippet:

app/
  Http/
    Controllers/
resources/
  views/
routes/
  web.php

Where should you place a new controller named ProductController.php?

medium

A. app/Http/Controllers/ProductController.php

B. resources/views/ProductController.php

C. routes/ProductController.php

D. app/ProductController.php

Solution

1. Step 1: Locate where controllers go in Laravel

   Controllers are placed inside app/Http/Controllers folder to handle requests.

2. Step 2: Check other folders for controllers

   resources/views is for templates, routes is for route files, and app root is not for controllers.

3. Final Answer:

   app/Http/Controllers/ProductController.php -> Option A

4. Quick Check:

   Controllers = app/Http/Controllers [OK]

Hint: Controllers live in app/Http/Controllers [OK]

Common Mistakes:

• Placing controllers in views folder
• Putting controllers directly in app root
• Confusing routes folder with controllers

4. You try to access a configuration value in Laravel using config('database.host') but get an error. What is the most likely cause?

medium

A. The routes/web.php file is empty

B. The database.php config file is missing or misnamed

C. The app/Http/Controllers folder is missing

D. The resources/views folder has no Blade files

Solution

1. Step 1: Understand how config() works in Laravel

   The config() helper reads values from files in the config folder, like database.php.

2. Step 2: Identify cause of error

   If database.php is missing or misnamed, config('database.host') cannot find the value, causing an error.

3. Final Answer:

   The database.php config file is missing or misnamed -> Option B

4. Quick Check:

   Missing config file = error on config() call [OK]

Hint: Check config files exist for config() calls [OK]

Common Mistakes:

• Blaming routes or controllers for config errors
• Ignoring missing or misnamed config files
• Assuming views affect config values

5. You want to add a new API endpoint in your Laravel app. Which folders must you update to add a route, controller, and response view correctly?

hard

A. Update routes/api.php, create controller in app/Http/Controllers, and add view in resources/views

B. Update routes/web.php, create controller in app/Models, and add view in public

C. Update config/api.php, create controller in app/Http/Controllers, and add view in resources/assets

D. Update routes/api.php, create controller in app/Http/Middleware, and add view in resources/views

Solution

1. Step 1: Identify where API routes are defined

   API routes go in routes/api.php to separate them from web routes.

2. Step 2: Locate correct controller and view folders

   Controllers belong in app/Http/Controllers, and views go in resources/views.

3. Step 3: Check incorrect options

   app/Models is for data models, public is for assets, config/api.php is not standard, and middleware folder is for request filters.

4. Final Answer:

   Update routes/api.php, create controller in app/Http/Controllers, and add view in resources/views -> Option A

5. Quick Check:

   API route + controller + view folders = Update routes/api.php, create controller in app/Http/Controllers, and add view in resources/views [OK]

Hint: API routes in routes/api.php, controllers in app/Http/Controllers [OK]

Common Mistakes:

• Putting API routes in routes/web.php
• Creating controllers in wrong folders
• Adding views outside resources/views