Remove default ENV to allow user provide environment variables via env files #3925
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.
NextJS app allow user define environment variables by providing a
.env.local
file in/app/
.Those related lines in the Dockerfile are setting values to the environment variables, which will be passed in as
process.env
, which ranked as the top one in the loading orderThis PR is removing these default variables so that user can just mount a
.env.local
file to set environment variable, which can avoid include the sensitive information in the docker-compose file.