Skip to content

Clarifying what happens with --env=prod + APP_ENV=prod #10705

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Clarifying what happens with --env=prod + APP_ENV=prod #10705

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions configuration/dot-env-changes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,10 @@ important changes:
other environments. You can also create a ``.env.test`` file for test-environment
overrides.

* E) If you pass the ``--env=`` flag when running ``bin/console``, this value will
override your ``APP_ENV`` environment variable (if set). And so, if you pass
``--env=prod``, the DotEnv component *will* try to load your ``.env*`` files.

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.

Expand Down