It is often helpful to have different configuration values based on the environment the application is running in. In order to do thatÂ Laravel utilizes the DotEnv PHP library by Vance Lucas.
Unfortunately Laravel considers that application can run only in one environment per server and fetches all custom configuration parameters only fromÂ
.env file. If you don’t have it, just copy
But there are times I need different values on the same machine. Most common use case is testing. I need one
.env for my local development and then I would need a different database in my test cases.
Laravel way this can be done by switching
.env.local and then
.env. After tests are finished files should be switched back again. Other way that is proposed is to include testing variables inside
phpunit.xml file, check the section
<env name="APP_ENV" value="testing"/>
<env name="CACHE_DRIVER" value="array"/>
<env name="SESSION_DRIVER" value="array"/>
<env name="QUEUE_DRIVER" value="sync"/>
Use different environment files
Checking Application.php (/vendor/laravel/framework/src/Illuminate/Foundation/Application.php) there is a protected variable $environmentFile that is set to ‘.env’.
Environment file is loaded during bootstrapping. Looking further you will also findÂ a method calledloadEnvironmentFrom($file).
All you need to do now is call this method with proper environment file.
Since I only needed to switch filesÂ for testing I added .env.testing.example and .env.testing. I think it is wise to exclude any real config data from version control and exclude .env.testing (does .gitignore ring any bells?)
LetsÂ call thisÂ method in /tests/TestCase.php
public function createApplication()
$app = require __DIR__.'/../bootstrap/app.php';
//THIS IS IT :)