Skip to content

.env file output #31

Closed
Closed
@alexquick

Description

@alexquick

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?

Activity

joho

joho commented on May 3, 2017

@joho
Owner

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

alexquick commented on May 3, 2017

@alexquick
ContributorAuthor

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

joho commented on May 4, 2017

@joho
Owner

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

joho

joho commented on Sep 14, 2017

@joho
Owner

Fixed in #35

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

      Participants

      @joho@alexquick

      Issue actions

        .env file output · Issue #31 · joho/godotenv