Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit c53d770

Browse filesBrowse files
mertingenwouterj
mertingen
authored and
wouterj
committed
Update configuration.rst to aviod misunderstanding
We shouldn't deploy the ".env.local" file for the production environment variables. We just need to add the ".env" file into Git and manually create a new ".env.local" file on the production machine. In the old expression says, "deploying" and it might be a misunderstanding in this way. I changed it to "creating". Old expression: 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.
1 parent 4f76354 commit c53d770
Copy full SHA for c53d770

File tree

1 file changed

+1
-1
lines changed
Filter options

1 file changed

+1
-1
lines changed

‎configuration.rst

Copy file name to clipboardExpand all lines: configuration.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -688,7 +688,7 @@ Configuring Environment Variables in Production
688688
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
689689

690690
In production, the ``.env`` files are also parsed and loaded on each request. So
691-
the easiest way to define env vars is by deploying a ``.env.local`` file to your
691+
the easiest way to define env vars is by creating a ``.env.local`` file on your
692692
production server(s) with your production values.
693693

694694
To improve performance, you can optionally run the ``dump-env`` command (available

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.