You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a few environments in which it becomes very hard if not impossible to provide CLI args to get desired behavior. Would it be possible to read the desired Poe root through an env var?
$ export POE_ROOT='foo'
$ poe ...
would then be equal to
$ poe --root='foo'
but with the CLI options obviously taking precedence.
The text was updated successfully, but these errors were encountered:
Having a default value for the --root arg from the environment sounds reasonable. I suspect we'd need to make sure it doesn't collide with any env vars already used by poe (like POE_ROOT) to avoid unexpected behavior when for example invoking the poe CLI from within a poe task – more thought required on that question.
There are a few environments in which it becomes very hard if not impossible to provide CLI args to get desired behavior. Would it be possible to read the desired Poe root through an env var?
would then be equal to
$ poe --root='foo'
but with the CLI options obviously taking precedence.
The text was updated successfully, but these errors were encountered: