Skip to content
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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

writeEnv: add append option #3

Open
marktani opened this issue Jan 7, 2018 · 3 comments
Open

writeEnv: add append option #3

marktani opened this issue Jan 7, 2018 · 3 comments

Comments

@marktani
Copy link
Contributor

marktani commented Jan 7, 2018

Currently, writeEnv overwrites the file content of .env. An append option would be super useful to support existing .env files.

For example, in the node-advanced boilerplate, I use env var APP_SECRET that is gone after running writeEnv.
This was referenced Jan 7, 2018
Closed
Merged
@kbrandwijk
Copy link
Member

Yeah, that process should be more intelligent. Maybe using dotenv-save.

@marktani
Copy link
Contributor Author

marktani commented Jan 8, 2018

For now, I'm using replaceInFiles(['.env], ...) instead of writeEnv and it fulfills my needs 🙂 So I'm not sure if we need to change the way writeEnv works.

@kbrandwijk
Copy link
Member

There's also a singular version replaceInFile for single file replacement by the way...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feature(writeEnv) append instead of overwrite .env graphql-boilerplates/graphql-boilerplate-install
2 participants
@kbrandwijk @marktani