What's the correct way to set ENV variables in Laravel 5?

Question

在laravel 4我们有：

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

默认。

但是在laravel 5中，它改为：

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

另外，他们排除了.gitignore中的.env。*行，现在它有：

.env

并添加文件.env.example：

APP_ENV=local
APP_KEY=SomeRandomString
DB_USERNAME=homestead
DB_PASSWORD=homestead

那么，如果我有两个以上的环境，那么我现在必须将它们全部放在一个.env文件中吗？例如：

APP_ENV=local
DB_PASSWORD=123

APP_ENV=alpha
DB_PASSWORD=456

如果我没有.env文件，Laravel如何知道我在使用什么环境？

Hi Heihachi，在laravel-5，在哪个文件夹.ENV文件位于。我找不到该文件。你能帮我么。 — Nana Partykar, 9月4日，15日11:48

clone45 · Accepted Answer · 2015-11-16 01：13：19Z

你可以做到与Laravel 4完全相同：

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

*.env文件只用于将不应放入VCS的敏感数据。Laravel 4也是如此

但是似乎在最近的日子里，默认的detectEnvironment改为：

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

所以您可以使用PC名称或ENV文件中的设置变量。

如果在主env文件中使用基于ENV的环境检测（默认.env文件需要添加：

APP_ENV=local

当然local这里是当地的环境，你可以把它改成production或者dev

目前我看到的最重要的问题是，您需要记住何时进行生产以将此.env文件内容更改APP_ENV=local为APP_ENV=production这样，在我看来，更好的方法是基于PC名称的旧的默认方法。

现在ENV文件。如果您使用基于ENV的环境检测，您应该仅放入ENV文件中：

APP_ENV=local

现在，您可以为不同的环境创建单独的ENV文件，例如：

.local.env：

 MY_DB=testdb

.production.env：

MY_DB=productiondb

现在在bootstrap.environment.php档案你可以modfiy：

if (file_exists(__DIR__.'/../.env'))
{
    Dotenv::load(__DIR__.'/../');
}

成：

if (file_exists(__DIR__.'/../.env'))
{
    Dotenv::load(__DIR__.'/../');

    if (getenv('APP_ENV') && file_exists(__DIR__.'/../.' .getenv('APP_ENV') .'.env')) {
        Dotenv::load(__DIR__ . '/../', '.' . getenv('APP_ENV') . '.env');
    }   
}

根据APP_ENV主env文件加载额外的env文件。

现在，您将能够一直在其他配置文件中使用它： $_ENV['MY_DB']

谢谢，没有修改environment.php我只能使用一个.env文件，对吧？我也可以只设一次APP_ENV吗？ — 平和, 十月14 '14在5:48
而我认为这个新的“方式”比旧的方式更方便。因为每次从github / bitbucket部署时，都必须使用所需的环境和变量创建.env文件。 — 平和, 十月14 '14在6:09
@Heihachi是的，它只会.env默认加载文件，所以你不能有2个ENV与不同的环境的设置。当然，如果可以，一个文件就足够了，如果你在配置文件中使用不同环境的不同env变量名称。 — MarcinNabiałek, 十月14 '14在6:55
但是如果我们没有.env文件呢？Laravel如何知道我们正在使用什么环境？我正在处理本地虚拟机并打印App :: environment（）; 并显示本地。它如何知道我在当地的环境，而不是生产？ — 平和, 十月14 '14在8:05
@MarcinNabiałek - 你应该更新你的答案 - 因为我认为只有ENV仍然在最新的L5？ — 劳伦斯, 11月5日'14在12:09

Hirnhamster · Answer 2 · 2016-01-17 13：58：50Z

对于刚升级到5.2的人：

您不能再使用静态Dotenv::load()方法。使用以下代替：

$dotenv = new Dotenv\Dotenv(__DIR__ . '/../', '.' . getenv('APP_ENV') . '.env'); // Laravel 5.2
$dotenv->load();

在bootstrap/app.php。

//编辑Soo ..在挖掘这个过去一小时后，我可以在这里添加一些额外的信息：

Laravel使用.env文件进行配置
默认情况下，应用程序根目录下的文件“.env”将被加载
您可以通过env()帮助函数访问这些.env文件中的值，或直接通过PHP的本机getenv()功能访问这些值。虽然你只应该这样做来填充你的配置文件（见/config/*.php），因为那些可以被缓存。
.env文件加载到DetectEnvironment类中。我在调试时发现这有助于设置断点。请注意(new Dotenv($app->environmentPath(), $app->environmentFile()))->load();：由于使用已设置的任何环境值将不会被覆盖！（您将不得不使用这样做 - 这驱使我坚果，因为homestead设置变量在php-fpm配置，你不能通过.env文件更改）load() overload()APP_ENVlocal/etc/php/7.0/fpm/php-fpm.conf
在编写单元测试时，通常会继承TestCase，将APP_ENV变量设置为测试（通过refreshApplication()- 使用putenv()来覆盖默认local值）

你救了我的一天我的.env突然没有加载。我不得不改变你的代码让它为我工作：$dotenv = new Dotenv\Dotenv(__DIR__.'/../');这可能是未来的一个问题吗？ — C. de la Fonteijne, Feb 1 '16 at 14:44

AVN · Answer 3 · 2017-01-11 14：27：58Z

您可以检查如何正确设置。如何为Laravel 5开发人员设计多种环境

基于MarcinNabiałek，我删除了它的一部分，并把它放在正确的文件中加载它正确。

thefuzzy0ne · Answer 4 · 2016-07-17 13：05：45Z

我只想为Laravel 5.1提供我的解决方案，这是更简单的IMHO。在bootstrap / app.php中，我有（刚刚应用程序实例化之后）：

$app->beforeBootstrapping(\Illuminate\Foundation\Bootstrap\DetectEnvironment::class, function() use ($app) {
    $suffix = (env('APP_ENV')) 
        ? '.'.env('APP_ENV') 
        : '';
    $app->loadEnvironmentFrom('.env'.$suffix);
});

不需要任何检查或错误处理。如果找不到文件，Laravel将默认为“production”。

就这些。

score 0 · Answer 5

事实上，.env默认情况下不能有多个文件，而在.gitignore中被排除在外的事实是有意的，是管理环境的预期方式。该.env文件不应该是版本控制，应该根据环境进行配置。.env设置您的环境和所有环境变量。

那么，如果我有两个以上的环境，那么我现在必须将它们全部放在一个.env文件中吗？

不，您将.env在每个地方安装一个文件。区别在于该文件的内部。

另外，因为该.env文件只是一个键值存储，任何后续的声明将覆盖以前的声明。在您的示例中，Laravel将永远不会看到您的“本地”设置。

起初看起来似乎很奇怪，但是这种新的默认系统实际上通常更容易，而且不容易出现“4.2方式”所具有的问题，因为没有逻辑错误的地方。

如果我没有.env文件，Laravel如何知道我在使用什么环境？

它根本不会运行。在.env文件中也是一个APP_KEY声明，Laravel不会没有运行。没有.env文件，您将收到500服务器错误。

来自 http://stackoverflow.com/questions/26346299/whats-the-correct-way-to-set-env-variables-in-laravel-5

What's the correct way to set ENV variables in Laravel 5?

clone45 · Accepted Answer · 2015-11-16 01:13:19Z

You can do it exactly the same as in Laravel 4:

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

*.env file are just used to put sensitive data that shouldn't be put into VCS. The same is in Laravel 4

but is seems that in last days default detectEnvironment was changed to:

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

so you can use either setting variable from PC name or from ENV file.

If you use ENV based environment detection in main env file (by default .env file you need to add:

APP_ENV=local

Of course local here is local environment, you can change it into production or dev

At the moment the most important issue I see is that you need to remember when going on production to change this .env file content from APP_ENV=local to APP_ENV=production so in my opinion much better method is the old default method based on PC names.

Now ENV files. If you use ENV based environment detection, you should put into your ENV file only:

APP_ENV=local

Now you can create separate ENV files for your different environments for example:

.local.env :

 MY_DB=testdb

.production.env :

MY_DB=productiondb

and now in bootstrap.environment.php file you can modfiy:

if (file_exists(__DIR__.'/../.env'))
{
    Dotenv::load(__DIR__.'/../');
}

into:

if (file_exists(__DIR__.'/../.env'))
{
    Dotenv::load(__DIR__.'/../');

    if (getenv('APP_ENV') && file_exists(__DIR__.'/../.' .getenv('APP_ENV') .'.env')) {
        Dotenv::load(__DIR__ . '/../', '.' . getenv('APP_ENV') . '.env');
    }   
}

to load extra env file based on APP_ENV from main env file.

Now you will be able to use it in your other configuration file as always: $_ENV['MY_DB']

Thanks, without modifying environment.php i can use only one .env file, right? also i can set APP_ENV just once? — Heihachi, Oct 14 '14 at 5:48
And i think this new "way" is more convenient than an old one. Because everytime you deploy from github/bitbucket you will have to create .env file with required environment and variables. — Heihachi, Oct 14 '14 at 6:09
@Heihachi Yes, it will only load .env file by default so you couldn't have 2 ENV with settings for different environments. Of course if you can, one file is enough if you will use in your config files different env variables names for different environments. — Marcin Nabiałek, Oct 14 '14 at 6:55
But what if we have no .env file at all? How laravel will know what environment we are using? I am working on local VM and printing App::environment(); and it shows local. How does it know that i'm on local environment, not production? — Heihachi, Oct 14 '14 at 8:05
@MarcinNabiałek - you should update your answer - as I think only ENV remains in the latest L5? — Laurence, Nov 5 '14 at 12:09

Hirnhamster · Answer 7 · 2016-01-17 13:58:50Z

For those who just upgraded to 5.2:

You cannot longer use the static Dotenv::load() method. Use the following instead:

$dotenv = new Dotenv\Dotenv(__DIR__ . '/../', '.' . getenv('APP_ENV') . '.env'); // Laravel 5.2
$dotenv->load();

in bootstrap/app.php.

//edit Soo.. after digging into this for the past hour I might as well add some additional info here:

Laravel uses .env files for configuration
By default, the file ".env" in the root directory of the application is loaded
You can access the values within those .env files via the env() helper function or directly via PHP's native getenv() function. Although you should only do so to fill your config files (see /config/*.php), because those can be cached.
the .env files are loaded in the DetectEnvironment class. I found this helpful while debugging to set breakpoints. Please take note of the line (new Dotenv($app->environmentPath(), $app->environmentFile()))->load();: Since it uses load() any environment value that has already been set will not be overwritten! (You would have to use overload() to do so - this drove me nuts because homestead sets the APP_ENVvariable to local in the php-fpm config /etc/php/7.0/fpm/php-fpm.conf and you cannot change it via .env file)
when writing unit tests, you usually inherit from TestCase, which sets the APP_ENV variable to testing (via refreshApplication() -- using putenv() to override the default localvalue)

You saved my day. My .env suddenly didn't load. I had to change your code to get it to work for me: $dotenv = new Dotenv\Dotenv(__DIR__.'/../'); Could this be a problem in the future? — C. de la Fonteijne, Feb 1 '16 at 14:44

avn · Answer 8 · 2017-01-11 14:27:58Z

You can check on how to setup properly. How to Setup Multiple Environment for Laravel 5 Developers Way

Based on Marcin Nabiałek, I removed some part of it, and put it in proper file to load it right.

thefuzzy0ne · Answer 9 · 2016-07-17 13:05:45Z

I just wanted to contribute my solution for Laravel 5.1, which is slightly simpler IMHO. In bootstrap/app.php, I have (just after where the Application is instantiated):

$app->beforeBootstrapping(\Illuminate\Foundation\Bootstrap\DetectEnvironment::class, function() use ($app) {
    $suffix = (env('APP_ENV')) 
        ? '.'.env('APP_ENV') 
        : '';
    $app->loadEnvironmentFrom('.env'.$suffix);
});

There's no need for any checking or error handling. Laravel will default to "production" if the file is not found.

That is all.

score 0 · Answer 10

The fact that you can't have more than one .env file by default and that it's excluded in .gitignore is intentional and is the intended way to manage environments. The .env file should not be in version control and should be configured per environment. .env sets your environment and all environment variables.

So, if i have more than 2 environments, do i have to set all of them in a single .env file now?

No. You would have a .env file in each place that you have your application installed. The difference is in what is inside that file.

Additionally, because the .env file is simply a key-value store, any subsequent declarations would overwrite previous ones. In your example, Laravel would never see your "local" settings.

It seems odd at first, but this new default system is actually generally easier and less prone to the issues the "4.2 way" had/has, as there's no place for logic errors.

If i would have no .env file, how laravel will know what environment i am using?

It wouldn't run at all. In the .env file is also an APP_KEY declaration, which Laravel will not run without. Without a .env file, you would get a 500 server error.

来自 http://stackoverflow.com/questions/26346299/whats-the-correct-way-to-set-env-variables-in-laravel-5

You are here

What's the correct way to set ENV variables in Laravel 5? 在Laravel 5中设置ENV变量的正确方法是什么？

5答案正确答案

What's the correct way to set ENV variables in Laravel 5?

5 Answers 正确答案

友情链接

搜索表单

用户登录

You are here

What's the correct way to set ENV variables in Laravel 5? 在Laravel 5中设置ENV变量的正确方法是什么？

5答案 正确答案

What's the correct way to set ENV variables in Laravel 5?

5 Answers 正确答案

友情链接

5答案正确答案