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.

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

.env file output #31

Closed
alexquick opened this issue May 2, 2017 · 4 comments
Closed

.env file output #31

alexquick opened this issue May 2, 2017 · 4 comments

Comments

@alexquick
Copy link
Contributor

Hi, I've got a use case where it would be beneficial to be able to output .env files as well as read them. Is that something you'd be interested in a PR for or is it out of scope for this project?

@joho
Copy link
Owner

joho commented May 3, 2017

HI @alexquick my first instinct is that it would be out of scope. I don't want to dismiss it out of hand though. Maybe if you could elaborate on the usecase it would be an easier call one way or the other.

@alexquick
Copy link
Contributor Author

Sure! I'm contributing to an application that manages the environments of other applications. As part of that it spends a fair degree of time working with dotenv files representing the environments of those applications, which it needs to both read and write.

Having one golang library to be able to roundtrip dotenv files would be nice. But on the other hand I understand that it's a pretty fringe use case.

@joho
Copy link
Owner

joho commented May 4, 2017

Let's give it a whirl. If it proves problematic it can always be extracted later.

@joho
Copy link
Owner

joho commented Sep 14, 2017

Fixed in #35

@joho joho closed this as completed Sep 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants