Laravel 5 configuration - environments and overriding

Question

I installed fresh Laravel 5 copy.

My detectEnvironment function is defined this way:

$app->detectEnvironment(function()
{
    return \'local\';
           


        

Answer 1

There's a package that brings the cascading config system back to Laravel 5.

Disclaimer: I am the author.

Answer 2

It is easy to configure Laravel 5 environment.

1. Open your root application folder and find ".env.example",
2. Copy and rename into ".env",
3. Please fit ".env" file into your environment,
4. If you use GIT, make sure you don't push this file to your GIT repository. For 'complete explanation', I write this configuration here.

Edited;

I quote from the developer in His github repository readme.md file;

phpdotenv is made for development environments, and generally should not be used in production. In production, the actual environment variables should be set so that there is no overhead of loading the .env file on each request. This can be achieved via an automated deployment process with tools like Vagrant, chef, or Puppet, or can be set manually with cloud hosts like Pagodabox and Heroku.

So, you need to create ".env" file per machine and don't use ".env" file in your production server.

Answer 3

For me it looks like defect in Laravel 5 dev branch. I was able to work around by adding manual environment detection and configuration. This code does it.

'default' => $app->environment()=='testing'?'sqlite':'mysql',

Answer 4

Although in documentation for Laravel dev (5.0) there is info that configuration will cascade it's not true. I have tested it about 2 weeks ago and it seems at the moment the only way to have different values for environments is using ENV file where you put custom values for current environment. Putting settings in directories won't work as it used to work however it's possible it will change or maybe has been already changed for last 2 weeks.