{"id":16198,"date":"2020-07-13T17:28:35","date_gmt":"2020-07-13T17:28:35","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=16198"},"modified":"2021-10-30T06:29:17","modified_gmt":"2021-10-30T06:29:17","slug":"directory-structure-of-laravel","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/directory-structure-of-laravel\/","title":{"rendered":"Directory Structure of Laravel"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

The image is showing the files and directories of laravel<\/strong>. It is automatically created when we create a project using a composer or laravel installer.<\/p>\n\n\n\n

Let’s we overview these files and directories.<\/p>\n\n\n\n

First we understand about files<\/strong>.<\/p>\n\n\n\n

.env <\/h3>\n\n\n\n

This is an environment file where we put credentials (username password and other information) which will use in the project. Ex. Database username, password, database name, any third party creds like Mailgun, Redis, etc.<\/p>\n\n\n\n

We can change the path of this file for more security purpose. Go to vendor\\vlucas\\phpdotenv\\src\\Loader <\/strong>and change it in the constructor.<\/p>\n\n\n\n

.gitattribute<\/h3>\n\n\n\n

It just hint about git. Don’t think more about this file.<\/p>\n\n\n\n

.gitignore<\/h3>\n\n\n\n

Here we put file name which will not commit in bitbucket or git repos.<\/p>\n\n\n\n

artisan<\/h3>\n\n\n\n

When we run PHP <\/strong>artisan command in terminal or command prompt actually we trigger this file only. It runs The Artisan Application.<\/p>\n\n\n\n

composer.json<\/h3>\n\n\n\n

This is the configuration file that specifies all dependencies or dependencies for development purpose.<\/p>\n\n\n\n

composer.lock<\/h3>\n\n\n\n

It lock the version of dependencies. So, In future when we’ll install the dependency, Install same version.<\/p>\n\n\n\n

package.json<\/h3>\n\n\n\n

This is related to frontend dependency. you may find the which frontend dev dependencies (with version) is installed. Ex.vue,jquery etc.<\/p>\n\n\n\n

server.php<\/h3>\n\n\n\n

This file allows us to emulate Apache’s “mod_rewrite” functionality from the built-in PHP web server.<\/p>\n\n\n\n

webpack.mix.js<\/h3>\n\n\n\n

It compiles scss or less or js files.<\/p>\n\n\n\n

api.php<\/h3>\n\n\n\n

Here we can register API routes for our application.<\/p>\n\n\n\n

channels.php<\/h3>\n\n\n\n

Here we may register all of the event broadcasting channels that our application supports.<\/p>\n\n\n\n

console.php<\/h3>\n\n\n\n

Here we may define all of our Closure based console commands and run on terminal. ex. PHP artisan inspire or PHP artisan foobar etc.<\/p>\n\n\n\n

web.php<\/h3>\n\n\n\n

we can register web routes for our application. <\/p>\n\n\n\n

Ex. Route::get(‘\/’,’RegisterController@index’); Route::post(‘\/register’,’RegisterController@register’);<\/p>\n\n\n\n

Directories<\/h2>\n\n\n\n

App Directory<\/h3>\n\n\n\n

The app directory contains the core code of your application.<\/p>\n\n\n\n

Bootstrap Directory<\/h3>\n\n\n\n

The bootstrap directory contains the app.php file which bootstraps the framework.<\/p>\n\n\n\n

Config Directory<\/h3>\n\n\n\n

The config directory, as the name implies, contains all of your application’s configuration files.<\/p>\n\n\n\n

Database Directory<\/h3>\n\n\n\n

The database directory contains your database migrations, model factories, and seeds.<\/p>\n\n\n\n

Public Directory<\/h3>\n\n\n\n

The public directory contains the index.php file, which is the entry point for all requests entering your application and configures autoloading. This directory also houses your assets such as images, JavaScript, and CSS.<\/p>\n\n\n\n

Resources Directory<\/h3>\n\n\n\n

The resources directory contains your views as well as your raw, un-compiled assets such as LESS, SASS, or JavaScript. This directory also houses all of your language files.<\/p>\n\n\n\n

Routes Directory<\/h3>\n\n\n\n

The routes directory contains all of the route definitions for your application.<\/p>\n\n\n\n

Storage Directory<\/h3>\n\n\n\n

The storage directory contains your compiled Blade templates, file-based sessions, file caches, and other files generated by the framework.<\/p>\n\n\n\n

Test Directory<\/h3>\n\n\n\n

This directory contain the test code of our project for testing purpose.<\/p>\n\n\n\n

vendor Directory<\/h3>\n\n\n\n

This directory contains the core files of the composer so no need to worry about this and here we don’t create files\/folders writes code in existing files.<\/p>\n\n\n