Slide 1
Most trusted JOB oriented professional program
DevOps Certified Professional (DCP)

Take your first step into the world of DevOps with this course, which will help you to learn about the methodologies and tools used to develop, deploy, and operate high-quality software.

Slide 2
DevOps to DevSecOps – Learn the evolution
DevSecOps Certified Professional (DSOCP)

Learn to automate security into a fast-paced DevOps environment using various open-source tools and scripts.

Slide 2
Get certified in the new tech skill to rule the industry
Site Reliability Engineering (SRE) Certified Professional

A method of measuring and achieving reliability through engineering and operations work – developed by Google to manage services.

Slide 2
Master the art of DevOps
Master in DevOps Engineering (MDE)

Get enrolled for the most advanced and only course in the WORLD which can make you an expert and proficient Architect in DevOps, DevSecOps and Site Reliability Engineering (SRE) principles together.

Slide 2
Gain expertise and certified yourself
Azure DevOps Solutions Expert

Learn about the DevOps services available on Azure and how you can use them to make your workflow more efficient.

Slide 3
Learn and get certified
AWS Certified DevOps Professional

Learn about the DevOps services offered by AWS and how you can use them to make your workflow more efficient.

previous arrow
next arrow

Directory Structure of Laravel

The image is showing the files and directories of laravel. It is automatically created when we create a project using a composer or laravel installer.

Let’s we overview these files and directories.

First we understand about files.


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.

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


It just hint about git. Don’t think more about this file.


Here we put file name which will not commit in bitbucket or git repos.


When we run PHP artisan command in terminal or command prompt actually we trigger this file only. It runs The Artisan Application.


This is the configuration file that specifies all dependencies or dependencies for development purpose.


It lock the version of dependencies. So, In future when we’ll install the dependency, Install same version.


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


This file allows us to emulate Apache’s “mod_rewrite” functionality from the built-in PHP web server.


It compiles scss or less or js files.


Here we can register API routes for our application.


Here we may register all of the event broadcasting channels that our application supports.


Here we may define all of our Closure based console commands and run on terminal. ex. PHP artisan inspire or PHP artisan foobar etc.


we can register web routes for our application.

Ex. Route::get(‘/’,’RegisterController@index’); Route::post(‘/register’,’RegisterController@register’);


App Directory

The app directory contains the core code of your application.

Bootstrap Directory

The bootstrap directory contains the app.php file which bootstraps the framework.

Config Directory

The config directory, as the name implies, contains all of your application’s configuration files.

Database Directory

The database directory contains your database migrations, model factories, and seeds.

Public Directory

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.

Resources Directory

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.

Routes Directory

The routes directory contains all of the route definitions for your application.

Storage Directory

The storage directory contains your compiled Blade templates, file-based sessions, file caches, and other files generated by the framework.

Test Directory

This directory contain the test code of our project for testing purpose.

vendor Directory

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.