Skip to content

Commit 569fc12

Browse files
committed
minor #18850 [Config] [Configuration] Emphasize env vars purpose (alexandre-daubois)
This PR was merged into the 5.4 branch. Discussion ---------- [Config] [Configuration] Emphasize env vars purpose Fix #14745 Commits ------- eab31f0 [Configuration] Emphasize env vars purpose
2 parents 3143b33 + eab31f0 commit 569fc12

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

configuration.rst

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -599,6 +599,15 @@ The values of these options are resolved at runtime (only once per request, to
599599
not impact performance) so you can change the application behavior without having
600600
to clear the cache.
601601

602+
.. note::
603+
604+
Environment variables are designed to store information that can
605+
dynamically change in a production environment, such as an API
606+
key that may have an expiration date. This information could be updated
607+
without having to redeploy the application. Thus, not everything is a good
608+
candidate for env vars, and
609+
:ref:`parameters <configuration-parameters>` should be used in other cases.
610+
602611
This example shows how you could configure the application secret using an env var:
603612

604613
.. configuration-block::

0 commit comments

Comments
 (0)