Jul 13, 2023 · Jan 19, 2022
diff --git a/configuration.rst b/configuration.rst
 the easiest way to define env vars is by deploying a ``.env.local`` file to your
 production server(s) with your production values.

 To improve performance, you can optionally run the ``dump-env`` command (available
 in :ref:`Symfony Flex <symfony-flex>` 1.2 or later):
 To improve performance, you can optionally run the ``dotenv:dump`` command (available
 in :ref:`Symfony Flex <symfony-flex>` 1.2 or later). The command is not registered by default.
 In order to enable it, you must add it to their services.yaml file:

 .. code-block:: yaml

    services:
        Symfony\Component\Dotenv\Command\DotenvDumpCommand:
            - '%kernel.project_dir%/.env'
            - '%kernel.environment%'

 On PHP >= 8, the two arguments can be removed when autoconfiguration is enabled (which is the default):

 .. code-block:: yaml

    services:
        Symfony\Component\Dotenv\Command\DotenvDumpCommand: ~

 Running command:

 .. code-block:: terminal

    # parses ALL .env files and dumps their final values to .env.local.php
    $composerdump-env prod
    $php bin/console dotenv:dump prod

 After running this command, Symfony will load the ``.env.local.php`` file to
 get the environment variables and will not spend time parsing the ``.env`` files.
diff --git a/deployment.rst b/deployment.rst

    .. code-block:: terminal

        $composerdump-env prod
        $php bin/console dotenv:dump prod

    The generated file will contain all theconfiguration stored in ``.env``. If you
    The generated file will contain all theconfigurations stored in ``.env``. If you
    want to rely only on environment variables, generate one without any values using:

    .. code-block:: terminal

        $composerdump-env prod --empty
        $php bin/console dotenv:dump prod --empty

 C) Install/Update your Vendors
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Original file line number	Diff line number	Diff line change
Expand Up		@@ -772,13 +772,30 @@ In production, the ``.env`` files are also parsed and loaded on each request. So
		the easiest way to define env vars is by deploying a ``.env.local`` file to your
		production server(s) with your production values.

		To improve performance, you can optionally run the ``dump-env`` command (available
		in :ref:`Symfony Flex <symfony-flex>` 1.2 or later):
		To improve performance, you can optionally run the ``dotenv:dump`` command (available
		in :ref:`Symfony Flex <symfony-flex>` 1.2 or later). The command is not registered by default.
		In order to enable it, you must add it to their services.yaml file:

		.. code-block:: yaml

		services:
		Symfony\Component\Dotenv\Command\DotenvDumpCommand:
		- '%kernel.project_dir%/.env'
		- '%kernel.environment%'

		On PHP >= 8, the two arguments can be removed when autoconfiguration is enabled (which is the default):

		.. code-block:: yaml

		services:
		Symfony\Component\Dotenv\Command\DotenvDumpCommand: ~

		Running command:

		.. code-block:: terminal

		# parses ALL .env files and dumps their final values to .env.local.php
		$composerdump-env prod
		$php bin/console dotenv:dump prod

		After running this command, Symfony will load the ``.env.local.php`` file to
		get the environment variables and will not spend time parsing the ``.env`` files.
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -164,14 +164,14 @@ most natural in your hosting environment.

		.. code-block:: terminal

		$composerdump-env prod
		$php bin/console dotenv:dump prod

		The generated file will contain all theconfiguration stored in ``.env``. If you
		The generated file will contain all theconfigurations stored in ``.env``. If you
		want to rely only on environment variables, generate one without any values using:

		.. code-block:: terminal

		$composerdump-env prod --empty
		$php bin/console dotenv:dump prod --empty

		C) Install/Update your Vendors
		~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down