Jake Kagan
01/19/2023, 3:04 PMworkspace.yml
file..the documents say to set DAGSTER_HOME
, so i have it as DAGSTER_HOME='L:\work\Dagster\volumes dagster-daemon run'
when i run dagit
in the command line, and its showing in deployment that no daemon is running: No recent heartbeat
i have a schedule defined as a test,with default_status=DefaultScheduleStatus.RUNNING
- and it shows up under the module's schedules tab. but no deamon running.Martin Picard
01/19/2023, 3:11 PMexport DAGSTER_HOME
or otherwise script it so they are both using itdaniel
01/19/2023, 3:27 PMJake Kagan
01/19/2023, 3:49 PMdagster-deamon run
part to it because that's what i saw in the docs. basically im hoping to run dagit and the daemon at the same timedagster-daemon run
and start up the daemon..how would i then look at it from the ui standpointdaniel
01/19/2023, 4:07 PMMartin Picard
01/19/2023, 4:07 PMdaniel
01/19/2023, 4:07 PMCarlos Pega
01/19/2023, 5:36 PMdaniel
01/19/2023, 5:49 PMCarlos Pega
01/19/2023, 5:50 PMdaniel
01/19/2023, 5:52 PMDAGSTER_HOME=$PWD dagster dev
would work for that if its an option for youCarlos Pega
01/19/2023, 5:53 PMdaniel
01/19/2023, 9:31 PMCarlos Pega
01/19/2023, 9:56 PMJake Kagan
01/19/2023, 11:44 PMdagster-daemon run
on one terminal, then dagit
on another... the thing is when i run dagit, it warns me that it's gonna store in temp instead of where DAGSTER_HOME
is - and then when in the ui, it shows a yellow tiangle issue for deploymentMartin Picard
01/20/2023, 8:07 AMJake Kagan
01/20/2023, 2:01 PMdagster dev
feature is awesome, thank you so much