Skip to content

Commit 809ba3c

Browse files
authored
Update deployment.rst
Updated file recommended for use when using .env files to manage environment variables for the application.
1 parent 0e74d26 commit 809ba3c

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

deployment.rst

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -134,14 +134,13 @@ B) Configure your Environment Variables
134134
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
135135

136136
Most Symfony applications read their configuration from environment variables.
137-
While developing locally, you'll usually store these in ``.env`` and ``.env.local``
138-
(for local overrides). On production, you have two options:
137+
While developing locally, you'll usually store these in `.env files <https://symfony.com/doc/current/configuration.html#configuring-environment-variables-in-env-files>`_. On production, you have two options:
139138

140139
1. Create "real" environment variables. How you set environment variables, depends
141140
on your setup: they can be set at the command line, in your Nginx configuration,
142141
or via other methods provided by your hosting service;
143142

144-
2. Or, create a ``.env.local`` file like your local development.
143+
2. Or, create a ``.env.prod.local`` file containing values specific to your production environment.
145144

146145
There is no significant advantage to either of the two options: use whatever is
147146
most natural in your hosting environment.

0 commit comments

Comments
 (0)