docs: better explain how environment variables work in production #27189
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.
馃摎 Description
We see a lot of people still being confused about why their
.env
or.env.prod
files are not being read in production, especially people coming from Laravel or other PHP frameworks where.env
files are being picked up automatically in production. Nuxt does it slightly differently, since it can be deployed to serverless or edge environments where a traditional filesystem isn't even available. So hopefully this will clear the confusion and explain the reasoning behind this design decision.This PR also lists some specific ways that env variables can be set in production so people are not left wondering how to do it.