Skip to content

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

Open

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.

Activity

  1. tcj commented on Nov 21, 2022

    @tcj
    CollaboratorAuthor

    I believe this also complicates the 'custom token' handling, which is itself represented by another currently-open issue.

  2. tcj commented on Nov 22, 2022

    @tcj
    CollaboratorAuthor

    note: the pattern I'm speaking of (which is not used in pysofar, or is bypassed) is load_dotenv(find_dotenv())

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions