Skip to content

handling of .env file sometimes hardcodes file location to user's home directory #32

Description

@tcj

I'm going spare on the specifics right now — but there are cases where this client will only read/honor the .env file that is in the user's home directory, rather than following the normal logic dotenv provides.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions