I try to find out why my env() helper always returns null. This causes trouble especially in app.php file, where are env() helpers widely used by default. Perhaps any mysterious server setting?
My env file:
APP_ENV=production
APP_KEY=base64:mymagickey=
APP_DEBUG=false
APP_LOG_LEVEL=info
APP_URL=http://www.example.com
etc...
EDIT - I tried following:
php artisan cache:clear
php artisan view:clear
php artisan config:cache
and ofcourse, i am using env helper like this: env('APP_ENV')
But still no success. The wierd part is, that $_ENV php variable contains every single variable from .env file.
env(...) function will not work after you cached the config. (starting from laravel 5.2 till current 5.7)
The Laravel documentation says
If you are using the
config:cachecommand during deployment, you must make sure that you are only calling theenvfunction from within your configuration files, and not from anywhere else in your application.
So the correct answer would be to
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.
And I quoted it from the same documentation
But for a quick fix this will do:
php artisan config:clear
And now it should be clear why, when you tried config:cache, it did not help, even though it clears the config prior to caching.
Hope this command will save you
php artisan config:clear
Five most important commands if your Laravel is not working as expected after some modifications in .env or database folder or because of any other modifications. Here is full explanation: https://www.youtube.com/watch?v=Q1ynDMC8UGg
php artisan config:clear
php artisan cache:clear
php artisan view:clear
php artisan route:clear
composer dump-autoload