8000 [Config] Shortening the list to make it more scanable by ThomasLandauer · Pull Request #17675 · symfony/symfony-docs · GitHub
[go: up one dir, main page]
Skip to content

[Config] Shortening the list to make it more scanable #17675

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
Jan 13, 2023
Merged

[Config] Shortening the list to make it more scanable #17675

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
19 changes: 10 additions & 9 deletions configuration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -347,7 +347,7 @@ configuration file using a special syntax: wrap the parameter name in two ``%``
.. note::

If some parameter value includes the ``%`` character, you need to escape it
by adding another ``%`` so Symfony doesn't consider it a reference to a
by adding another ``%``, so Symfony doesn't consider it a reference to a
parameter name:

.. configuration-block::
Expand Down Expand Up @@ -409,17 +409,18 @@ The files stored in ``config/packages/`` are used by Symfony to configure the
the application behavior by changing which configuration files are loaded.
That's the idea of Symfony's **configuration environments**.

A typical Symfony application begins with three environments: ``dev`` (for local
development), ``prod`` (for production servers) and ``test`` (for
:doc:`automated tests </testing>`). When running the application, Symfony loads
A typical Symfony application begins with three environments:
* ``dev`` for local development,
* ``prod`` for production servers,
* ``test`` for :doc:`automated tests </testing>`.
When running the application, Symfony loads
the configuration files in this order (the last files can override the values
set in the previous ones):

#. ``config/packages/*.yaml`` (and ``*.xml`` and ``*.php`` files too);
#. ``config/packages/<environment-name>/*.yaml`` (and ``*.xml`` and ``*.php`` files too);
#. ``config/services.yaml`` (and ``services.xml`` and ``services.php`` files too);
#. ``config/services_<environment-name>.yaml`` (and ``services_<environment-name>.xml``
and ``services_<environment-name>.php`` files too).
#. The files in ``config/packages/*.<extension>``;
#. the files in ``config/packages/<environment-name>/*.<extension>``;
#. ``config/services.<extension>``;
#. ``config/services_<environment-name>.<extension>``.

Take the ``framework`` package, installed by default, as an example:

Expand Down
0