fix: prevent old env variables from persisting during deployment#128
Open
Chandraveersingh1717 wants to merge 1 commit intometacall:masterfrom
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently, the .env file is written using fs.appendFileSync. This causes
environment variables from previous deployments to remain in the file.
As a result, outdated values may persist and override the new configuration.
For example:
Old .env
PORT=3000
New deployment
PORT=8080
With appendFileSync the file becomes:
PORT=3000
PORT=8080
This PR replaces appendFileSync with writeFileSync so the .env file is
overwritten instead of appended. This ensures that only the latest
environment variables are present after deployment.