You are browsing the Symfony 4 documentation, which changes significantly from Symfony 3.x. If your app doesn't use Symfony 4 yet, browse the Symfony 3.4 documentation.
Nov 2018 Changes to .env & How to Update
Nov 2018 Changes to .env & How to Update¶
In November 2018, several changes were made to the core Symfony recipes related
.env file. These changes make working with environment variables easier
and more consistent - especially when writing functional tests.
If your app was started before November 2018, your app does not require any changes to keep working. However, if/when you are ready to take advantage of these improvements, you will need to make a few small updates.
What Changed Exactly?¶
But first, what changed? On a high-level, not much. Here's a summary of the most important changes:
- A) The
.env.distfile no longer exists. Its contents should be moved to your
.envfile (see the next point).
- B) The
.envfile is now commited to your repository. It was previously ignored via the
.gitignorefile (the updated recipe does not ignore this file). Because this file is committed, it should contain non-sensitive, default values. Basically, the
.env.distfile was moved to
- C) A
.env.localfile can now be created to override environment variables for your machine. This file is ignored in the new
- D) When testing, your
.envfile is now read, making it consistent with all other environments. You can also create a
.env.testfile for test-environment overrides.
- E) One further change to the recipe in January 2019 means that your
.envfiles are always loaded, even if you set an
APP_ENV=prodenvironment variable. The purpose is for the
.envfiles to define default values that you can override if you want to with real environment values.
There are a few other improvements, but these are the most important. To take advantage of these, you will need to modify a few files in your existing app.
Updating My Application¶
If you created your application after November 15th 2018, you don't need to make any changes! Otherwise, here is the list of changes you'll need to make - these changes can be made to any Symfony 3.4 or higher app:
Create a new config/bootstrap.php file in your project. This file loads Composer's autoloader and loads all the
.envfiles as needed (note: in an earlier recipe, this file was called
Update your bin/console file to load the new
1 2 3 4 5 6 7 8 9 10
# .gitignore # ... ###> symfony/framework-bundle ### - /.env + /.env.local + /.env.local.php + /.env.*.local # ...
1 2 3 4 5 6 7 8 9
# Unix $ mv .env .env.local $ git mv .env.dist .env # Windows $ mv .env .env.local $ git mv .env.dist .env You can also update the `comment on the top of .env`_ to reflect the new changes.
This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.