Skip to content

Commit 57d0f6b

Browse files
committed
minor #10705 Clarifying what happens with --env=prod + APP_ENV=prod (weaverryan)
This PR was submitted for the master branch but it was merged into the 4.1 branch instead (closes #10705). Discussion ---------- Clarifying what happens with --env=prod + APP_ENV=prod Closes symfony/recipes#497 (comment) Commits ------- 3e9c091 Clarifying what happens with --env=prod + APP_ENV=prod
2 parents 4e24dbc + 3e9c091 commit 57d0f6b

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

configuration/dot-env-changes.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,10 @@ important changes:
3030
other environments. You can also create a ``.env.test`` file for test-environment
3131
overrides.
3232

33+
* E) If you pass the ``--env=`` flag when running ``bin/console``, this value will
34+
override your ``APP_ENV`` environment variable (if set). And so, if you pass
35+
``--env=prod``, the DotEnv component *will* try to load your ``.env*`` files.
36+
3337
There are a few other improvements, but these are the most important. To take advantage
3438
of these, you *will* need to modify a few files in your existing app.
3539

0 commit comments

Comments
 (0)