Skip to content

Revamped the main configuration file #11690

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.

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
Jun 12, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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 _build/redirection_map
Original file line number Diff line number Diff line change
Expand Up @@ -417,3 +417,7 @@
/workflow/state-machines /workflow/introduction
/workflow/usage /workflow
/introduction/from_flat_php_to_symfony2 /introduction/from_flat_php_to_symfony
/configuration/environment_variables /configuration/env_var_processors
/configuration/configuration_organization /configuration
/configuration/environments /configuration
/configuration/configuration_organization /configuration
7 changes: 3 additions & 4 deletions best_practices/configuration.rst
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,8 @@ application behavior.
.. best-practice::

Define the infrastructure-related configuration options as
:doc:`environment variables </configuration/environment_variables>`. During
development, use the ``.env`` and ``.env.local`` files at the root of your
project to set these.
:ref:`environment variables <config-env-vars>`. During development, use the
``.env`` and ``.env.local`` files at the root of your project to set these.

By default, Symfony adds these types of options to the ``.env`` file when
installing new dependencies in the app:
Expand Down Expand Up @@ -84,7 +83,7 @@ layer of configuration that's not needed because you don't need or want these
configuration values to change on each server.

The configuration options defined in the ``services.yaml`` may vary from one
:doc:`environment </configuration/environments>` to another. That's why Symfony
:ref:`environment <configuration-environments>` to another. That's why Symfony
supports defining ``config/services_dev.yaml`` and ``config/services_prod.yaml``
files so that you can override specific values for each environment.

Expand Down
2 changes: 1 addition & 1 deletion bundles.rst
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ SecurityBundle, DebugBundle, etc.) They are also used to add new features in
your application via `third-party bundles`_.

Bundles used in your applications must be enabled per
:doc:`environment </configuration/environments>` in the ``config/bundles.php``
:ref:`environment <configuration-environments>` in the ``config/bundles.php``
file::

// config/bundles.php
Expand Down
Loading