Homestead APP ENV not working

Level 9

I'm noticing this too. A vagrant reload --provision doesnt work either. Any insight on this would be appriciated.

https://github.com/laravel/laravel/commit/430134864642346498631ad562765d69599d6b39

Level 8

You just pull from laravel/laravel last commits? Use instead (for now) your .env file in the root directory of the project. Add to your .env file the following:

APP_ENV=custom

and

APP_DEBUG=yes

Level 3

Can we just delete variables from Homestead.yaml?

Level 9

@jrean No, I haven't pulled the bleeding edge commits, still riding v4.2.11 which Composer gives me.

Level 8

Ah ok, sorry. What is the version you use?

vagrant -v
vagrant box list laravel/homestead

It should be "laravel/homestead (virtualbox, 0.2.0)"

If not, update the box

vagrant box update --box laravel/homestead
vagrant reload --provision

Level 9

Im on 0.2.0, vagrant reload or vagrant reload --provisionneither reloads the APP_ENV but a vagrant destroy and vagrant up fixes it, but shouldn't really be necessary.

Level 8

Ok great ; But now, if you change APP_ENV to "FOO" for testing ... Then perform a vagrant reload, does the change is applied?

Level 3

@jrean, that doesn't work, i tried that many times.

Level 8

@heihachi88 what doesn't work? The above commands I asked to perform or the change I asked after @lasseal trick/fix?

Level 3

@jrean

Changing APP_ENV to "FOO" then vagrant reload or vagrant reload --provision didn't work.

Level 8

That means it is not reflecting your APP_ENV changes... Hum, weird. Just for testings again, if you drop and stop setting ENV trough your Homestead.yml but instead directly within a .env file as documented here: http://laravel.com/docs/4.2/configuration#protecting-sensitive-configuration

Does your changes are reflected and work?

Level 3

.env:

APP_ENV=haha

var_dump(getenv('APP_ENV'):

"local"

Seems like "local" is hardcoded somewhere in homestead.

1 like

https://github.com/laravel/laravel/blob/master/bootstrap/start.php

Level 8

[This answer is ONLY working for Laravel 4.x (not for Laravel ~5.0)]

Yes because you are running from homestead.

You have to tweak the detection method :)

For example:

$env = $app->detectEnvironment(function()
{
    return getenv('APP_ENV') ?: 'local';
});

1 like

Level 8

https://laracasts.com/search?q=environment

Level 9

I'm running

$env = $app->detectEnvironment(function() {    
    return getenv('APP_ENV') ? getenv('APP_ENV') : 'local';
});

but still it doesn't pick up any changes to APP_ENV in homestead.yaml.

Level 3

@jrean

It's an outdated code, bro. I don't have this in bootstrap/start.php (I am using Laravel 5 "develop" branch)

$env = $app->detectEnvironment(array(
'local' => array('homestead'),
));

Level 8

I based my answers to @lasseal saying 4.2 sorry!!

"No, I haven't pulled the bleeding edge commits, still riding v4.2.11 which Composer gives me."

So simply use a .env file and put APP_ENV=local or whatever you want.

Level 8

And by the way bootstrap/environment.php has been removed. So we only work with .env file and key/value. We don't care about detection method anymore. See Taylor comment and commit.

https://github.com/laravel/laravel/commit/430134864642346498631ad562765d69599d6b39

Level 3

Homestead uses APP_ENV in Homestead.yaml, not in .env

rawfan

Level 19

@heihachi88, just throw that out and use .env as your only place to define APP_ENV (and also APP_DEBUG).

1 like

Level 8

@rawfan is right. It's what I advised @heihachi88 in a previous post (page 1)

ballistic101

Level 1

I was having the same problem, and eventually solved it in the following way:

As stated above, there was an entry in Homestead.yaml for APP_ENV. I got rid of those as the posts above say, but that did not resolve the problem.
I found in homestead: /etc/php5/fpm/php-fpm.conf there are two lines at the bottom which say: env[APP_ENV] = 'local'

I commented them out, then ran: sudo service php5-fpm restart

That resolved the issue and now APP_ENV is getting the proper value.

For the record, this all comes about because the Dotenv module is run in "immutable" mode, so the pre-existing variable (in $_SERVER) does not get overwritten.

1 like

spar_x

Level 2

I am having pretty much the same problem but it is not related to the APP_ENV key.

I set another variable in my homestead.yaml called "HOME". I set it to XXX, and then later changed it to YYY.. and doing either vagrant reload or vagrant reload --provision refuses to update the variable to YYY. It is stuck on XXX and it does not want to get updated. This is very problematic that values get stuck like that and refused to get changed.. even custom variables!!! I don't want to have to destroy my box as I have lots of mysql databases installed and configured inside my homestead VM.

Has anyone figured out this riddle?

spar_x