Config:cache makes variables in .env null

@skovmand

Relevant ?

If you are using the config:cache command during deployment, you must make sure that you are only calling the env function from within your configuration files, and not from anywhere else in your application.

If you are calling env from within your application, it is strongly recommended you add proper configuration values to your configuration files and call env from that location instead, allowing you to convert your env calls to config calls.

Yeah. Thanks! Where did you find it?

It's actually semi buried in the docs:

https://laravel.com/docs/5.2/upgrade#upgrade-5.2.0

Thanks. That's it. I have been pulling my hair out over this one.

@skovmand no problem! Cheers

It's actually semi buried in the docs:

I was looking for that (for the other thread about config), and I just couldn't find it. I thought maybe I'd imagined it!

The Laravel docs are really well written, but a bit patchy in places.

Worth mentioning is that if you did call config:cache during local development, you can undo this by deleting the bootstrap/cache/config.php file

Worth mentioning is that if you did call config:cache during local development, you can undo this by deleting the bootstrap/cache/config.php file

Or you could artisan config:clear.

If you are using the config:cache command during deployment, you must make sure that you are only calling the env function from within your configuration files, and not from anywhere else in your application.

If you are calling env from within your application, it is strongly recommended you add proper configuration values to your configuration files and call env from that location instead, allowing you to convert your env calls to config calls.

Can anyone explain this further? What's the reason behind this change? And does it mean I cannot use env('SOME_VAR') at all anymore directly in my code except in the config files? Will it work or will it break if I utilize the config cache?

I find the explanation quite confusing...

I ended up adding each one into config/app.php (and referencing it as env('variable_name')) and just calling it properly with config('variable_name') from within the code

I think the main reason behind it is allowing users to set a default if the env file is missing the value requested

Thanks a lot !

This saved me after hours of struggle. Thank you!

Here's the best discussion of how to use the config files I've found:

https://scotch.io/tutorials/how-to-use-laravel-config-files

I also stumbled on this same matter and lost some hair on the process. Thus, I suggested this to be more explicit on the laravel/ideas repo, if anyone is interested as well.

@igorsantos07 They always welcome pull requests to the docs: https://github.com/laravel/docs