Home > Article > Backend Development > laravel directory structure
The default directory structure of the Laravel application attempts to provide a good starting point for both large and small applications. Of course, you can reorganize the application directory structure according to your preferences. Laravel does not have any restrictions on where classes are loaded - —As long as Composer can load them automatically.
The newly installed Laravel application contains many folders:
app
The directory contains the core code of the application;
The bootstrap
directory contains a few files for startup and automatic loading configuration of the framework, and a cache folder for containing startup files generated by the framework to improve performance;
config
directory contains All configuration files of the application;
database
directory contains data migration and filling files. If you like, you can also use it as the SQLite database storage directory;
public
The directory contains front-end controllers and resource files (images, JavaScript, CSS, etc.);
resources
The directory contains view files, native resource files (LESS, SASS, CoffeeScript), and localization files;
storage
The directory contains compiled Blade templates, file-based sessions, file caches, and other files generated by the framework. The folder is subdivided into app, framework, and logs subdirectories. , the app directory is used to store files to be used by the application, the framework directory is used to store files and caches generated by the framework, and finally, the logs directory contains the log files of the application;
tests
directory contains automated tests, where An out-of-the-box PHPUnit example has been provided;
vendor
directory contains Composer dependencies;
The core code of the application is located in the app directory By default, this directory is located under the App namespace and is automatically loaded by Composer via the PSR-4 autoloading standard. You can modify this namespace through the Artisan command app:name.
The app directory contains multiple subdirectories, such as Console, Http, Providers, etc. The Console and Http directories provide APIs that enter the core of the application. The HTTP protocol and CLI are two mechanisms for interacting with the application, but they do not actually contain application logic. In other words, they are just two ways of issuing commands to an application. The Console directory contains all Artisan commands, and the HTTP directory contains controllers, middleware, requests, etc.
Jobs
The directory is where queue tasks are placed. Tasks in the application can be queued or executed synchronously within the current request life cycle.
Events
The directory is where event classes are placed. Events can be used to notify other parts of the application that a given action has occurred, and provide flexible decoupled processing.
Listeners
The directory contains event handler classes. The handler receives an event and provides response logic after the event occurs. For example, the UserRegistered event can be processed by the SendWelcomeEmail listener.
Exceptions
The directory contains the application's exception handlers and is also a good place to handle any exceptions thrown by the application.
Note: Many classes in the app directory can be generated through Artisan commands. To view all valid commands, you can run the php artisan list make command in the terminal.
The above is the entire content of this article. I hope it will be helpful to everyone's study. For more related content, please pay attention to the PHP Chinese website!
Related recommendations:
About activemq stomp class code
Laravel5.2 uses Captcha to generate verification codes to implement login
The above is the detailed content of laravel directory structure. For more information, please follow other related articles on the PHP Chinese website!