Movatterモバイル変換

[0]ホーム
URL:

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

 Sign up
Appearance settings

Commit885d082

Browse files
committed
minor#16394 Update configuration.rst to avoid misunderstanding (mertingen)
This PR was submitted for the 6.0 branch but it was merged into the 4.4 branch instead.Discussion----------Update configuration.rst to avoid misunderstandingWe 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. Sothe easiest way to define env vars is by deploying a ``.env.local`` file to yourproduction server(s) with your production values.<!--If your pull request fixes a BUG, use the oldest maintained branch that containsthe bug (seehttps://symfony.com/releases for the list of maintained branches).If your pull request documents a NEW FEATURE, use the same Symfony branch wherethe feature was introduced (and `6.x` for features of unreleased versions).-->Commits-------c53d770 Update configuration.rst to aviod misunderstanding
2 parents4f76354 +c53d770 commit885d082

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎configuration.rst‎

Lines 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 bydeploying a ``.env.local`` fileto your
691+
the easiest way to define env vars is bycreating a ``.env.local`` fileon 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)
[8]ページ先頭
©2009-2025 Movatter.jp