From 0b70b3b3ff826aa856eac82f09826b083ef9673b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20Garz=C3=B3n?= Date: Sat, 29 Nov 2014 00:58:06 +0100 Subject: [PATCH 1/2] Update link title to match cookbook article title | Q | A | ------------- | --- | Doc fix? | yes | New docs? | no | Applies to | all | Fixed tickets | Article title updated in c9fe05b3b1a03fa196e80b22472eb3a7eb0be0a5 --- best_practices/configuration.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/best_practices/configuration.rst b/best_practices/configuration.rst index 3368c59589e..f4f0bed2504 100644 --- a/best_practices/configuration.rst +++ b/best_practices/configuration.rst @@ -158,7 +158,7 @@ Semantic Configuration: Don't Do It Don't define a semantic dependency injection configuration for your bundles. -As explained in `How to Expose a semantic Configuration for a Bundle`_ article, +As explained in `How to Load Service Configuration inside a Bundle`_ article, Symfony bundles have two choices on how to handle configuration: normal service configuration through the ``services.yml`` file and semantic configuration through a special ``*Extension`` class. @@ -179,5 +179,5 @@ through environment variables. Learn how to do it in the following article: .. _`feature toggles`: http://en.wikipedia.org/wiki/Feature_toggle .. _`execution environment`: http://symfony.com/doc/current/cookbook/configuration/environments.html .. _`constant() function`: http://twig.sensiolabs.org/doc/functions/constant.html -.. _`How to Expose a semantic Configuration for a Bundle`: http://symfony.com/doc/current/cookbook/bundles/extension.html +.. _`How to Load Service Configuration inside a Bundle`: http://symfony.com/doc/current/cookbook/bundles/extension.html .. _`How to Set external Parameters in the Service Container`: http://symfony.com/doc/current/cookbook/configuration/external_parameters.html From d59b8524fccdb53060c6f78b16d717493639f960 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20Garz=C3=B3n?= Date: Sat, 29 Nov 2014 11:42:01 +0100 Subject: [PATCH 2/2] Change links to symfony-docs relative without title --- best_practices/configuration.rst | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/best_practices/configuration.rst b/best_practices/configuration.rst index f4f0bed2504..136f8a3778c 100644 --- a/best_practices/configuration.rst +++ b/best_practices/configuration.rst @@ -74,9 +74,9 @@ add an extra 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 ``config.yml`` file usually vary from -one `execution environment`_ to another. That's why Symfony already includes -``app/config/config_dev.yml`` and ``app/config/config_prod.yml`` files so -that you can override specific values for each environment. +one :doc:`/cookbook/configuration/environments` to another. That's why Symfony +already includes ``app/config/config_dev.yml`` and ``app/config/config_prod.yml`` +files so that you can override specific values for each environment. Constants vs Configuration Options ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -158,10 +158,10 @@ Semantic Configuration: Don't Do It Don't define a semantic dependency injection configuration for your bundles. -As explained in `How to Load Service Configuration inside a Bundle`_ article, -Symfony bundles have two choices on how to handle configuration: normal service -configuration through the ``services.yml`` file and semantic configuration -through a special ``*Extension`` class. +As explained in :doc:`/cookbook/bundles/extension` article, Symfony bundles +have two choices on how to handle configuration: normal service configuration +through the ``services.yml`` file and semantic configuration through a special +``*Extension`` class. Although semantic configuration is much more powerful and provides nice features such as configuration validation, the amount of work needed to define that @@ -174,10 +174,7 @@ 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: -`How to Set external Parameters in the Service Container`_ +:doc:`/cookbook/configuration/external_parameters` .. _`feature toggles`: http://en.wikipedia.org/wiki/Feature_toggle -.. _`execution environment`: http://symfony.com/doc/current/cookbook/configuration/environments.html .. _`constant() function`: http://twig.sensiolabs.org/doc/functions/constant.html -.. _`How to Load Service Configuration inside a Bundle`: http://symfony.com/doc/current/cookbook/bundles/extension.html -.. _`How to Set external Parameters in the Service Container`: http://symfony.com/doc/current/cookbook/configuration/external_parameters.html