Skip to content

Provide custom path for .env.example #514

@Wiktor102

Description

@Wiktor102

Proposal

Add a new optional argument: examplePath that would set the path for the .env.example file. The current behavior would be the default if not provided.

My usecase

I'm using 2 separate envs for dev and prod: .env.development, and .env.production. I am dynamically loading the correct one. I'd like to make use of the safe option, but that means 2 .example files as currently the same filename as the env file is used. This defeats the purpose of the safe option, as nothing prevents those example files from diverging.

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

    Issue actions