[#8732] Minor tweaks

Author: weaverryan

configuration.rst

@@ -72,7 +72,7 @@ instance, the framework bundle is configured in ``config/packages/framework.yaml
         ]);
 
 The top-level key (here ``framework``) references configuration for a specific
-bundle (``FrameworkBundle`` in this case).
+bundle (:doc:`FrameworkBundle </reference/configuration/framework>` in this case).
 
 .. sidebar:: Configuration Formats
 
@@ -207,12 +207,30 @@ a controller - see :ref:`service-container-parameters`.
 .. _config-dot-env:
 .. _config-parameters-yml:
 
-The .env File
-~~~~~~~~~~~~~
+The .env File & Environment Variables
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 There is also a ``.env`` file which is loaded. Its contents become environment
 variables in the dev environment, making it easier to reference environment
-variables in your code.
+variables in your code. When you install packages, more environment variables are
+added to this file. But you can also add your own variables.
+
+Environment variables can be referenced in any other configuration files by using
+a special syntax. For example, if you install the ``doctrine`` package, then you
+will have an environment variable called ``DATABASE_URL`` in your ``.env`` file.
+This is referenced inside ``config/packages/doctrine.yaml``:
+
+.. code-block:: yaml
+
+    # config/packages/doctrine.yaml
+    doctrine:
+        dbal:
+            url: '%env(DATABASE_URL)%'
+
+            # the resolve: prefix will resolve parameters *inside* the env variable
+            # url: '%env(resolve:DATABASE_URL)%'
+
+For more details about environment variables, see :ref:`config-env-vars`.
 
 The ``.env`` file is special, because it defines the values that usually change
 on each server. For example, the database credentials on your local development

configuration/environments.rst

@@ -176,9 +176,10 @@ always run the application in the dev environment, independent of the
 Selecting the Environment for Console Commands
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-By default, Symfony commands are executed in the ``dev`` environment and with the
-debug mode enabled. Use the ``--env`` and ``--no-debug`` options to modify this
-behavior:
+By default, Symfony commands are executed in whatever environment is defined by
+the ``APP_ENV`` environment variable (usually configured in your ``.env`` file).
+
+Use the ``--env`` and ``--no-debug`` options to modify this behavior:
 
 .. code-block:: terminal
 
@@ -191,14 +192,6 @@ behavior:
     # 'test' environment and debug disabled
     $ php bin/console command_name --env=test --no-debug
 
-In addition to the ``--env`` and ``--no-debug`` options, the behavior of Symfony
-commands can also be controlled with the same environment variables used by
-``public/index.php``.
-
-These environment variables are very useful for production servers because they
-allow you to ensure that commands always run in the ``prod`` environment without
-having to add any command option.
-
 .. index::
    single: Environments; Creating a new environment
 

configuration/external_parameters.rst

@@ -10,6 +10,8 @@ credentials outside of your project code. Database configuration is one such
 example. The flexibility of the Symfony service container allows you to easily
 do this.
 
+.. _config-env-vars:
+
 Environment Variables
 ---------------------