Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
Update configuration.rst to avoid misunderstanding#16394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
94noni left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
perhaps target v5.4?
Even more, you can also reword the next paragraph and instead of usingcomposer dump-env, use the new same symfony featuresymfony/symfony#42610 :)
mertingen commentedJan 15, 2022
@94noni Thanks for referring to it. Should I change the base branch from 6.0 to 5.4? In addition to that, how does that command work? Should I change the following? From To Or |
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. Sothe easiest way to define env vars is by deploying a ``.env.local`` file to yourproduction server(s) with your production values.
wouterj commentedJan 19, 2022
Thanks@mertingen! I've merged this in 4.4, the oldest branch that we still maintain (and this change applies to). We're not sure how to document the new And to answer your question: |
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
.envfiles are also parsed and loaded on each request. Sothe easiest way to define env vars is by deploying a
.env.localfile to yourproduction server(s) with your production values.