Skip to content

Allow user to set env variables and do not always require a .env file - #4

Open
cmbiwer wants to merge 1 commit into
mainfrom
cmbiwer/env
Open

Allow user to set env variables and do not always require a .env file#4
cmbiwer wants to merge 1 commit into
mainfrom
cmbiwer/env

Conversation

@cmbiwer

@cmbiwer cmbiwer commented Aug 25, 2026

Copy link
Copy Markdown
Collaborator

This MR:

  • This function returns an empty dict. But if we just let it continue, the user could specify these variables in their environment.

There are probably several different things we could do. Raise a warning, have a strict/non-strict mode (i.e. fail if not found but continue if given the option to continue), etc. If you have a preference let me know.

This would be beneficial for setting up a default LLMS_JSON_FILE that users can share in a module. With this, then the user does not have to have a local .env file either, giving them more freedom to freely move around the filesystem and call wolf.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant