Update deployment docs with new .env loading

Author: cristi-contiu

deployment.rst

@@ -132,22 +132,29 @@ While developing locally, you'll usually store these in ``.env`` and ``.env.loca
 
 1. Create "real" environment variables. How you set environment variables, depends
    on your setup: they can be set at the command line, in your Nginx configuration,
-   or via other methods provided by your hosting service.
+   or via other methods provided by your hosting service (see note below)
 
-2. Or, create a ``.env.local`` file just like your local development (see note below)
+2. Or, create a ``.env.local`` file just like your local development.
 
 There is no significant advantage to either of the two options: use whatever is
 most natural in your hosting environment.
 
 .. note::
 
-    If you use the ``.env.*`` files on production, you may need to move your
-    ``symfony/dotenv`` dependency from ``require-dev`` to ``require`` in ``composer.json``:
+    If you use "real" environment variables on production you might not want your
+    application to process the ``.env.*`` files on every request. You can generate
+    an optimized ``.env.local.php`` which overrides all other configuration files:
 
     .. code-block:: terminal
 
-        $ composer remove symfony/dotenv
-        $ composer require symfony/dotenv
+        $ composer dump-env prod
+
+    The generated file will contain all the configuration stored in ``.env``. If you
+    want to rely only on environment variables, generate one without any values using:
+
+    .. code-block:: terminal
+
+        $ composer dump-env prod --empty
 
 C) Install/Update your Vendors
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~