You can also create a

dagster.yaml

file to further configure your setup

is there a "standard" choice of location for

$DAGSTER_HOME

in docker-based projects? like

/usr/src/app/.dagster_home

or something?

This guide uses

/opt/dagster/dagster_home

@sashank Using the CLI and GUI are working fine for me, but for some reason I'm not able to get runs executed with

execute_pipeline

to show up in the GUI or to write any data to

$DAGSTER_HOME

. As an MVP of this, I have

hello_dagster.py

that looks like this:

from dagster import execute_pipeline, pipeline, solid


@solid
def get_name(_):
    return "dagster"


@solid
def hello(context, name: str):
    <http://context.log.info|context.log.info>("Hello, {name}!".format(name=name))


@pipeline
def hello_pipeline():
    hello(get_name())


if __name__ == "__main__":
    execute_pipeline(hello_pipeline)

Before I executed the pipelines, I ran

$ export DAGSTER_HOME=$(pwd)/.dagster_home
$ mkdir -p .dagster_home

If I run

$ dagster pipeline execute -f hello_dagster.py

then the pipeline executes, the run shows up in dagit, and I can see entries added to

.dagster_home/history/runs

. If I run

$ python hello_dagster.py

then the pipeline executes, but I don't see anything written to

.dagster_home

and no new runs show up in dagit. Any ideas why this might be?