Laravel 5.2 not reading env file

Question

After upgrading to Laravel 5.2, none of my .env file values are being read. I followed the upgrade instructions; none of my config files were changed except auth.php. They were all working fine in previous version, 5.1.19

.env contains values such as

DB_DATABASE=mydb
DB_USERNAME=myuser

config/database.php contains

'mysql' => [
    'database' => env('DB_DATABASE', 'forge'),
    'username' => env('DB_USERNAME', 'forge'),
]

I get this error:

PDOException: SQLSTATE[HY000] [1045] Access denied for user 'forge'@'localhost' (using password: NO)

Clearly not pulling in my env config. This is affecting every single one of my config files, including third party such as bugsnag.

I also tried

php artisan config:clear
php artisan cache:clear

Update

Trying php artisan tinker

>>> env('DB_DATABASE')
=> null
>>> getenv('DB_DATABASE')
=> false
>>> config('database.connections.mysql.database')
=> "forge"
>>> dd($_ENV)
[]

I have tried installing a fresh copy of Laravel 5.2. I basically only copied in my "app" folder; no additional composer packages are included. Still having the same issue. I have other Laravel 5.2 projects on the same server that are working fine.

Are you sure the .env file is named only .env? Not .env.example? — James Elliott, Dec 22 '15 at 16:54
Andrew are you editing the .env file by the forge interface or uploading it? — Mark Davidson, Dec 22 '15 at 16:54
Or are you running this locally? If your running under artisan serve you need to restart it just in case that might be the case. — Mark Davidson, Dec 22 '15 at 16:55
@MarkDavidson editing it through vi in the command line, and no it's on a full server — andrewtweber, Dec 22 '15 at 16:55

Nisse Engström · Answer 1 · 2016-04-27 18:58:14Z

From the official Laravel 5.2 Upgrade Notes:

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.

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

php artisan config:cache solved it for me - nothing else had helped. Not even php artisan config:clear - thanks! — kair, May 15 '16 at 20:26
Laravel 5.3 php artisan config:clear is the only thing that worked for me — Dainis Abols, Jul 6 at 12:15
Laravel 5.4 - deployed on a VPS: php artisan config:clear worked for me. I didn't do config:cache before so it seemed a bit weird that I had to clear the cache. — Antonio, Jul 23 at 21:22

andrewtweber · Accepted Answer · 2015-12-22 19:44:03Z

up vote17down voteaccepted

Wow. Good grief. It's because I had an env value with a space in it, not surrounded by quotes

This

SITE_NAME=My website

Changed to this

SITE_NAME="My website"

Fixed it. I think this had to do with Laravel 5.2 now upgrading vlucas/phpdotenv from 1.1.1 to 2.1.0

edited Dec 22 '15 at 19:44

answered Dec 22 '15 at 19:38

andrewtweber

8,386124785

Same think - seems like spaces causes issues in .env under 5.2 where as in 5.1 it didn't. – thomthom Dec 29 '15 at 17:59

3

And this is one of my (many) bugbears with Laravel: it has a habit of sometimes silently ignoring and accepting a variety of configuration and/or other types of errors, with no indication anything has gone wrong. Given, this may be a "feature" of phpdotenv, but Laravel still knows there's a .env file that needs to be included, and that it wasn't successful, but doesn't bother to tell anyone. – dKen Apr 22 '16 at 14:07

add a comment

dKen · Answer 3 · 2016-04-22 14:32:29Z

If any of your .env variables contains white space, make sure you wrap them in double-quotes. For example:

SITE_NAME="My website"

Don't forget to clear your cache before testing:

php artisan config:cache;
php artisan config:clear;

Deric Lima · Answer 4 · 2016-09-01 14:02:42Z

I had a similar issue in my config/services.php and I solved using config clear and optimizecommands:

php artisan config:clear
php artisan optimize

dKen · Answer 5 · 2016-04-22 14:32:12Z

I missed this in the upgrade instructions:

Add an env configuration option to your app.php configuration file that looks like the following:'env' => env('APP_ENV', 'production')

Adding this line got the local .env file to be read in correctly.

I guess I got the same error, since my app was Laravel 4, then upgraded to 5.0, then to 5.1, etc. Probably missed adding this value in my app.php. Thanks for saving me a lot of time. Here's an upvote! — Bruno P. Kinoshita, Jun 2 '16 at 7:56

Waqleh · Answer 6 · 2017-06-16 10:58:23Z

Also additional to what @andrewtweber suggested make sure that you don't have spaces between the KEY= and the value unless it is between quotes

.env file e.g.:

...
SITE_NAME= My website
MAIL_PORT= 587
MAIL_FROM_NAME= websitename
...

to:

...
SITE_NAME="My website"
MAIL_PORT=587
MAIL_FROM_NAME=websitename
...

Mehar Singh · Answer 7 · 2016-12-22 04:16:22Z

A temp solution for me was to remove one dot from the $environmentFile = '..env'; to .env in vendor/laravel/framework/src/Illuminate/Foundation/Application.php

I know framework core files are not supposed to be modified, but this to highlight that Laravel sometimes not able to read .env file where there are two dots. Perhaps, its system specific.

There's already been an answer accepted here, so recommending to edit core files is probably not a good suggestion. — thebluefox, Dec 21 '16 at 11:35
Accepted answer didn't work for me, and I didn't mention not to modify core files of course. This is just to people know that something like this exists. — Mehar Singh, Dec 22 '16 at 4:15

搜索表单

用户登录

You are here

laravel env function not working

7 Answers

来自 https://stackoverflow.com/questions/34420761/laravel-5-2-not-reading-env-file

Laravel 5 Environment Detection Not Working

Best Answer(As Selected By breda)

.env Not Reading Variables Sometimes

友情链接