Introduction to Laravel

1. Laravel Versions
Version Release
5.0 February 4th, 2015
5.1 (LTS) June 9th, 2015
5.2 December 21st, 2015
5.3 August 23rd, 2016
5.4 January 24th, 2017
5.5(LTS) August 30th, 2017
5.6 February 7th, 2018

2. →First install xampp using this link:
https://www.apachefriends.org/download.html
→Laravel uses Composer to manage its
dependencies.
→So, before using Laravel, make sure you have
Composer installed on your machine.
→Link For Download and Install Composer:
https://getcomposer.org/

3. •After the Composer is installed, check the installation by typing the
Composer command in the command prompt as shown in the
following screenshot.

4. •Create a new directory anywhere in your system for your
new Laravel project.
•After that, move to path where you have created the new
directory and type the following command there to install
Laravel.
•D:tution>composer create-project --prefer-dist
laravel/laravel demo
•The above command will install Laravel in the current
directory and create project named demo.

5. •Start the Laravel service by executing the following
command.
•D:tution>demo>php artisan serve
Type http://127.0.0.1:8000 in any internet browser URL

6. Type http://127.0.0.1:8000 AND PRESS ENTER in any internet browser URL:

7. Directory Structure
of
Project demo:-

8. •contains the core code of your application.
•almost all of the classes in your application will be in this
directory.
•The bootstrap directory contains the app.php file which
bootstraps the framework.
•This directory also includes a cache directory which
contains framework generated files for performance
optimization such as the route and services cache files.

9. •The config directory, as the name implies, contains all of your
application's configuration files.
•The database directory contains your database migrations, model
factories, and seeds.
• If you wish, you may also use this directory to hold an SQLite
database.
•The public directory contains the index.php file, which is the entry
point for all requests entering your application and configures auto
loading.
•This directory also houses your assets such as images, JavaScript,
and CSS.

10. •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.
•The routes directory contains all of the route definitions for
your application.
•By default, several route files are included with Laravel:
api.php, channels.php, console.php and web.php.

11. •The api.php file contains routes that the
RouteServiceProvider places in the api middleware group,
which provides rate limiting.
•These routes are intended to be stateless, so requests
entering the application through these routes are intended to
be authenticated via tokens and will not have access to
session state.
•The channels.php file is where you may register all of the
event broadcasting channels that your application supports.

12. •The console.php file is where you may define all of your
Closure based console commands.
•Each Closure is bound to a command instance allowing a
simple approach to interacting with each command's IO
methods.
• Even though this file does not define HTTP routes, it
defines console based entry points (routes) into your
application.
•The web.php file contains routes that the
RouteServiceProvider places in the web middleware group,
which provides session state, CSRF protection, and cookie
encryption.
•If your application does not offer a stateless, RESTful API,
all of your routes will most likely be defined in the web.php

13. •This directory contains App storage, like file uploads etc.
Framework storage (cache), and application-generated
logs.
•This directory contains various test cases.
•This directory contains composer dependencies.

14. App Directory This is the application directory. It contains a variety of additional
directories, which are described below:
Console: All the artisan commands are stored in this directory.
Events: This directory stores events that your application can raise. Events may
be used to alert other parts of your application that a given action has occurred,
providing a great deal of flexibility and decoupling.
Exceptions: This directory contains your application's exception handler and is
also a good place to stick any exceptions thrown by your application.
Http: This directory contains your controllers, filters, and requests.
Jobs: This directory contains the queueable jobs for your application.
Listeners: This directory contains the handler classes for your events. Handlers
receive an event and perform logic in response to the event being fired. For
example, a UserRegistered event might be handled by a SendWelcomeEmail
listener.
Policies: This directory contains various policies of the application.