Skip to content

Commit 3aed2cf

Browse files
committed
Merge branch '5.2' into 5.3
* 5.2: Use APP_RUNTIME_ENV to define secrets
2 parents e20dee1 + 72c47d3 commit 3aed2cf

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

configuration/secrets.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ running:
4848

4949
.. code-block:: terminal
5050
51-
$ php bin/console secrets:generate-keys --env=prod
51+
$ APP_RUNTIME_ENV=prod php bin/console secrets:generate-keys
5252
5353
This will generate ``config/secrets/prod/prod.encrypt.public.php`` and
5454
``config/secrets/prod/prod.decrypt.private.php``.
@@ -78,7 +78,7 @@ Suppose you want to store your database password as a secret. By using the
7878
$ php bin/console secrets:set DATABASE_PASSWORD
7979
8080
# set your production value
81-
$ php bin/console secrets:set DATABASE_PASSWORD --env=prod
81+
$ APP_RUNTIME_ENV=prod php bin/console secrets:set DATABASE_PASSWORD
8282
8383
This will create a new file for the secret in ``config/secrets/dev`` and another
8484
in ``config/secrets/prod``. You can also set the secret in a few other ways:
@@ -256,7 +256,7 @@ your secrets during deployment to the "local" vault:
256256

257257
.. code-block:: terminal
258258
259-
$ php bin/console secrets:decrypt-to-local --force --env=prod
259+
$ APP_RUNTIME_ENV=prod php bin/console secrets:decrypt-to-local --force
260260
261261
This will write all the decrypted secrets into the ``.env.prod.local`` file.
262262
After doing this, the decryption key does *not* need to remain on the server(s).

0 commit comments

Comments
 (0)