laravel-5

Upgrade Guide 42
The App\Providers\ConfigServiceProvider may be removed from your service provider list in
your app.php configuration file.
Upgrading To 5.0 From 4.2 {#upgrade-upgrade-5.0}
Fresh Install, Then Migrate
The recommended method of upgrading is to create a new Laravel 5.0 install and then to copy your
4.2 site’s unique application files into the new application. This would include controllers, routes,
Eloquent models, Artisan commands, assets, and other code specific files to your application.
To start, install a new Laravel 5.0 application into a fresh directory in your local environment. Do
not install any versions newer than 5.0 yet, since we need to complete the migration steps for 5.0
first. We’ll discuss each piece of the migration process in further detail below.
Composer Dependencies & Packages
Don’t forget to copy any additional Composer dependencies into your 5.0 application. This includes
third-party code such as SDKs.
Some Laravel-specific packages may not be compatible with Laravel 5 on initial release. Check with
your package’s maintainer to determine the proper version of the package for Laravel 5. Once you
have added any additional Composer dependencies your application needs, run composer update.
Namespacing
By default, Laravel 4 applications did not utilize namespacing within your application code. So, for
example, all Eloquent models and controllers simply lived in the “global” namespace. For a quicker
migration, you can simply leave these classes in the global namespace in Laravel 5 as well.
Configuration
Migrating Environment Variables
Copy the new .env.example file to .env, which is the 5.0 equivalent of the old .env.php file. Set
any appropriate values there, like your APP_ENV and APP_KEY (your encryption key), your database
credentials, and your cache and session drivers.
Additionally, copy any custom values you had in your old .env.php file and place them in both
.env (the real value for your local environment) and .env.example (a sample instructional value for
other team members).
For more information on environment configuration, view the full documentation.