Laravel 5 app always using 'testing' environment configuration

Question

I have a Laravel 5 app with two environments and two configurations: testing (for PHPUnit configuration, in-memory db) and local (my development configuration).

Even whe

Answer 1

Laravel 5 doesn't cascade config files correctly anymore so your testing config file is overriding anything you have in your local config file.

Now you aren't supposed to have any subfolders for each environment, but rather set configuration settings inside the .env file in the root folder.

This file isn't checked in to the repo to ensure that nothing sensitive is checked into the repo. You should have a separate .env file for each environment your application is living.

TESTING

For php unit (functional) you can set env variables in the phpunit.xml file e.g..

For behat (acceptance) testing the Laracasts Laravel Behat extension allows you to create a .env.behat file to change the environment variables.

For phpspec (unit) testing well the environment shouldn't matter as your testing individual methods in isolation and mock everything else.

For selenium (integration / system / e2e) testing the environment variables should come from the .env file on the server wherever you are doing this testing.