Can you set

$DAGSTER_HOME

any way except an env var? Our project gets most of its configurations from a

.env

file, and isn't always set up with something that publishes

.env

values as env vars. If it's not possible I can certainly adjust, just wondering if there were a way to set the home value for a Dagster instance at startup time or something.

No, env vars are currently the only way of setting

$DAGSTER_HOME

. What does the ideal solution look like for you? Would wrapping

dagster

/

dagit

/

dagster-daemon

calls with a

python-dotenv

invocation work?

I think switching to

dotenv

with a Python layout may be ideal, if everyone on the team is up for it. (: Good to know about

python-dotenv

though, a CLI wrapper that promotes

.env

values to env vars could do the trick too.