Skip to content

Add the ability to specify global & project-level default .env filenames #6

Description

@jongpie

Currently, the plugin supports specifying an .env file using the flag --env - this is great when running commands via a terminal, but when using VS Code (or other IDEs), there's not a way to use anything other than the assumed default filename .env.

  • Users should be able to specify a global default filename, for situations where something other than .env is generally preferred
  • Users should also be able to specify a repo/project-level default filename, so they can easily switch between different environments/environment variables (e.g., dev.env vs prod.env)

I think that the global default filename (configured on someone's machine) would live outside of source control - there might be some value in having project-level defaults be committed to source control, but probably it should also just live outside of source control 🤔

Activity

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

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions