Skip to content

Mentioned %env(...)% variables in Best Practices book #7224

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

Merged
merged 1 commit into from
Dec 14, 2016
Merged

Mentioned %env(...)% variables in Best Practices book #7224

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
16 changes: 14 additions & 2 deletions best_practices/configuration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,8 +175,20 @@ Moving Sensitive Options Outside of Symfony Entirely

When dealing with sensitive options, like database credentials, we also recommend
that you store them outside the Symfony project and make them available
through environment variables. Learn how to do it in the following article:
:doc:`/configuration/external_parameters`.
through environment variables:

.. code-block:: yaml

# app/config/config.yml
doctrine:
dbal:
# ...
password: "%env(DB_PASSWORD)%"

.. versionadded:: 3.2
Support for runtime environment variables via the ``%env(...)%`` syntax was
added in Symfony 3.2. Prior to version 3.2, you needed to use the
:doc:`special SYMFONY__ variables </configuration/external_parameters>`.

.. _`feature toggles`: https://en.wikipedia.org/wiki/Feature_toggle
.. _`constant() function`: http://twig.sensiolabs.org/doc/functions/constant.html