Laravel’s folder structure

• Introduction
• Root directory
  • ## app Directory
  • bootstrap Directory
  • config Directory
  • database Directory
  • public Directory
  • resources Directory
  • routes Directory
  • storage Directory
  • tests Catalog
  • vendor Catalog
• App Directory
  • broadcasting Directory
  • console Directory
  • events Catalog
  • exceptions Catalog
  • ## http Directory
  • jobs Directory
  • listeners Directory
  • mail Directory
  • notifications Directory
  ## policies
  • Catalog
  providers
  • Catalog
  rules
  • Catalog

models

For this reason, we place Eloquent models in the app

Root Directory

App Directory

app Directory contains the core of the application code. Almost all classes in your application should go here. We'll look into the details of this directory in more depth later.

Bootstrap Directory

bootstrap Directory contains app.php for Bootstrap Framework document. This directory also contains a cache directory. The cache directory stores files generated by the framework to improve performance, such as routing and service cache files.

Config directory

config Directory, as the name suggests, contains all configuration files of the application . We encourage you to read through these documents to help familiarize you with all available options.

Database directory

database Directory contains data population and migration files and model factory classes . You can also use it as a SQLite database storage directory.

Public directory

public The directory contains the entry file index.php , which is the entry point for all requests entering the application. This directory also contains some of your resource files (such as images, JavaScript, and CSS).

Resources directory

resources The directory contains views and uncompiled resource files ( such as LESS, SASS or JavaScript). This directory also contains all your language files.

Routes directory

routes The directory contains all route definitions of the application. Laravel includes several routing files by default: web.php, api .php, console.php and channels.php. The

web.php file contains RouteServiceProvider routes placed in the web middleware group, which provides session state, CSRF protection, and cookie encryption . If your application does not provide a stateless, RESTful API, all routes should be defined in the web.php file. The .

api.php file contains the RouteServiceProvider route placed in the api middleware group, which provides frequency limiting. These routes are stateless, so requests coming into the application through these routes are intended to be authenticated via the token and do not have access to session state.

console.php The file is where all console command-based closure functions are defined. Each closure function is bound to a command instance and allows simple interaction with command line IO methods. Although these files do not define HTTP routes, it also defines console-based entry points (routes) into the application.

channels.php A place to register all event broadcast channels supported by your application.

Storage directory

storage The directory contains the compiled Blade template and session session generation files, cache files, and other files generated by the framework. This directory is subdivided into three subdirectories: app, framework, and logs. The app directory can be used to store any files generated by the application. framework The directory is used to store files and cache generated by the framework. Finally, the logs directory contains the application’s log files.

storage/app/public Can be used to store user-generated files, such as user avatars that need to be publicly accessible. You should create a public/storage soft link pointing to this directory. You can create this link directly through the php artisan storage:link command.

Tests directory

tests The directory contains automated test files. There are ready-made examples in PHPUnit for your reference. Each test class should be suffixed with Test. You can use the phpunit or php vendor/bin/phpunit command to run the tests.

Vendor Directory

vendor The directory contains all your Composer dependency packages.

App Directory

Most of your applications are located in the app directory. By default, this directory is namespace App and is automatically loaded by Composer using the PSR-4 autoloading standard. The

app directory contains additional various directories, such as: Console, Http and Providers. Think of the Console and Http directories as providing APIs to the core of your application. Both the HTTP protocol and the CLI are mechanisms for interacting with applications, but do not actually contain application logic. In other words, they are two ways of issuing commands to your application. The Console directory contains all Artisan commands, while the Http directory contains your controllers, middleware, and requests.

When you use the make Artisan command to generate a class, various other directories will be generated under the app directory. So, for example, the app/Jobs directory will not exist until you execute the make:job Artisan command to generate a job class

{tip} Many Classes are generated in the app directory through Artisan commands. To see the available commands, run the php artisan list make command in your terminal.

Broadcasting Directory

Broadcasting Directory contains all broadcast channels for the application kind. These classes are generated using the make:channel command. This directory does not exist by default, but it will be created when you create the first channel. To learn more about channels, check out the documentation on event broadcasting.

Console Directory

Console directory contains all custom Artisan commands for the application. These commands can be generated using the make:command command. This directory also houses the console kernel, where you can register custom Artisan commands and define scheduled tasks.

event :generate and make:event Artisan commands to create. Events Directory placement event class. Events can be used to alert other parts of the application that a given action has occurred, providing great flexibility and decoupling.

The directory contains the application's exception handling and is also a A good place to put any exceptions thrown by your application. If you want to customize how exceptions are logged and rendered, you should modify the Handler class in this directory.

Http Directory

Http Directory contains your controllers, middleware and form requests. Almost all the logic for handling requests coming into the application is placed in this directory.

make :job Artisan command, it will be created. Jobs Directory houses the application's queueable jobs. Jobs can be scheduled by the application or run synchronously during the lifetime of the current request. Jobs that run synchronously during the current request are sometimes called "commands" because they are an implementation of the command pattern.

It will be created when event:generate or make:listener Artisan command is executed. Listeners The directory contains event handling classes. An event listener receives an event instance and executes logic in response to the event being triggered. For example, a UserRegistered event might be handled by a SendWelcomeEmail listener.

This directory does not exist by default, but if you execute

Artisan command and it will be created. Mail The directory contains all the classes used by the application to send mail. The mail object allows you to build a mail class that encapsulates all logic. In this simple class, you can use the Mail::send method to send emails.

This directory does not exist by default, but if you execute

Artisan command that will be created. Notifications The directory contains all "transactional" notifications sent by the application, such as simple notifications about events that occur in the application. Laravel's notification functionality abstracts sending notifications through various drivers (such as email, Slack, SMS or stored in a database).

make :policy

Policies The directory contains the application's authorization policy classes. Policies are used to determine whether a user can perform a given operation on a resource. For more information, view the licensing documentation.

Providers Directory

Providers The directory contains all service providers for the application. A service provider bootstraps an application by binding services in a service container, registering for events, or preparing to perform any other task for the application's incoming requests.

In a new Laravel application, this directory already contains some providers. Feel free to add your own providers to this directory as needed.

make :rule Artisan command that will be created. The Rules directory contains the application's custom validation rule objects. Rules are used to encapsulate complex validation logic in a simple object. For more information, view the validation documentation.