[Deployment] - More accurate local .env file recommendation #20785
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jdevinemt
changed the title
MrYamous
reviewed
Mar 21, 2025
|
@jdevinemt thanks ... and congrats on your first Symfony Docs contribution 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated file recommended for use when using .env files to manage environment variables for the application.
Previously, the recommended file was
.env.local, but if values added here would be overridden by.env.prodif present. It might be uncommon that someone would use a combination of.envand.env.prod, but it can't be assumed that it isn't the case. Using.env.prod.localis always going to be the last file processed by the dotenv component by default.It might be even better to not reference "prod" directly in
.env.prod.localand instead say.env.<env>.local, but prod is explicitly referenced elsewhere in this section/page. So I left the explicit reference.