sephi
05/07/2020, 5:12 AMdagster.yaml
configuration.
From the instance documentation I understand that it is read from the $DAGSTER_HOME
environment.
If the dagster.yaml
has the logic configuration per project while the $DAGSTER_HOME
env is per user, what is the correct manner to use the dagster.yaml
?
Where should it be saved and how could it be run per project?alex
05/07/2020, 5:38 AM$DAGSTER_HOME
points at a directory that can contain a dagster.yaml
to configure your “instance” which is akin to deployment or installsephi
05/07/2020, 7:22 AMDagster checks whether the environment variableIsn't this "environment variable" set per user? then it will always point to one directory with oneis setDAGSTER_HOME
dagster.yaml
file.
However each project that I use will want to run a different dagster.yaml
file, how do I configure that?alex
05/07/2020, 2:05 PMHowever each project that I use will want to run a differentOut of curiosity why is this? Can you tell me more about your set up? If you want to change your storage per project - you will have to set up multiple folders withfiledagster.yaml
dagster.yaml
and change your $DAGSTER_HOME
based on which project you are currently working on.
Our tools are currently set up to handle different pipelines/repositories using a shared storage, so I would consider using one instance for working on your projects, at least locally.sephi
05/07/2020, 8:13 PMalex
05/07/2020, 8:18 PMsephi
05/10/2020, 4:34 AMDAGSTER_HOME
environment to a folder on my dagster machine.
I set the dagster.yaml configuration to be exactly as in the documentation (just updating the base_dir).
I set the permissions of the folder to allow everyone to write to it.
When running the dagster - the job completes without any errors but I don't see any sqlite file.
Do I need to generate a sqlite file or will be generated automatically?
I'm I missing something?alex
05/11/2020, 3:34 PMbase_dir
- do you see the sqlite file in your DAGSTER_HOME
directory instead?