laravel-5

Release Notes 8
Folder Structure
To better express intent, the app/Commands directory has been renamed to app/Jobs. Additionally,
the app/Handlers directory has been consolidated into a single app/Listeners directory which
simply contains event listeners. However, this is not a breaking change and you are not required to
update to the new folder structure to use Laravel 5.1.
Encryption
In previous versions of Laravel, encryption was handled by the mcrypt PHP extension. However,
beginning in Laravel 5.1, encryption is handled by the openssl extension, which is more actively
maintained.
Laravel 5.0 {#releases-laravel-5.0}
Laravel 5.0 introduces a fresh application structure to the default Laravel project. This new structure
serves as a better foundation for building a robust application in Laravel, as well as embraces new
auto-loading standards (PSR-4) throughout the application. First, let’s examine some of the major
changes:
New Folder Structure
The old app/models directory has been entirely removed. Instead, all of your code lives directly
within the app folder, and, by default, is organized to the App namespace. This default namespace
can be quickly changed using the new app:name Artisan command.
Controllers, middleware, and requests (a new type of class in Laravel 5.0) are now grouped under the
app/Http directory, as they are all classes related to the HTTP transport layer of your application.
Instead of a single, flat file of route filters, all middleware are now broken into their own class files.
A new app/Providers directory replaces the app/start files from previous versions of Laravel
4.x. These service providers provide various bootstrapping functions to your application, such as
error handling, logging, route loading, and more. Of course, you are free to create additional service
providers for your application.
Application language files and views have been moved to the resources directory.
Contracts
All major Laravel components implement interfaces which are located in the illuminate/contracts
repository. This repository has no external dependencies. Having a convenient, centrally located set
of interfaces you may use for decoupling and dependency injection will serve as an easy alternative
option to Laravel Facades.
For more information on contracts, consult the full documentation.