Hi I am new to Dagster, I've run through the tutorials, which were great, but I'm wondering if it is possible to set Dagster up in such a manner that every pipeline executed via dagit/dagster is automatically added to a repository stored in a postgresdb??

hmm, I’m not 100% sure I know what you mean, but you can certainly use Postgres as backing storage for runs and events

@cat @max Thank you for reaching out! 🙂 So I have read this section of the docs, and i have added an env variable for $DAGSTER_HOME, as well as the dagster.yaml file (attached) However, when I run dagit without specifying a file or pipeline, it does not show me previous pipelines that were run...

Click on the “Runs” tab on the left hand side, under the Dagster logo?

"No runs to display. Use the Playground to start a pipeline."

And your pipeline has successfully run before while using the Postgres db?

So I am experimenting with the postgresdb, currently whenever I try to "Start Execution" of any given pipeline, I am greeted with: "Your instance has been configured to disable local execution. Please check the run launcher configuration on your dagster instance for more options." and to that end I haven't really found anything in the documentation about how to get around that

Oh the RemoteDagitRunLauncher is in the process of being deprecated, try just removing the run_launcher section from the config

I have already commented that section out in the config, which kind of adds to my confusion

Is there a small toggle next to start execution that lets you change to “launch execution”?

Nada :s

do you get an error if you hit “start execution” after removing run_launcher from your dagster.yaml?

Yes. I commented it out to begin with as reading the config it says "Provides an optional means to delegate the execution of pipeline runs", which I took as not default settings

whats the error you get when you try to start execution while a run launcher isnt configured?

So with my current config, which has the run launcher section commented out, whenever i attempt to "start execution" of a given pipeline I am greeted with the following error:

ah, removing the last section of the dagster.yaml will fix that issue

dagit:
  execution_manager:
    disabled: true # whether dagit can run pipelines in a sub process
    max_concurrent_runs: 10 # how many at a time

Thank you Cat! that does solve my problem related to execution, but my question still remains with the repository. Sorry for being a difficult customer 😬

so after running your pipeline, the runs tab is still empty?

No the run tab is updated with respects to that pipeline being executed, my question is whether dagster can be set up to show a history of sorts of everything that has been run, as well as their associated pipelines

the run tab should contain a history of every run that was executed with the current run storage. so if the run storage is changed, previous runs will not be viewable unless the run storage is changed back. does that answer the question?

No that is very clear! Thank you Cat 🙂 I guess I was hoping that the pipeline snapshot included in the run history would also include more in depth info on the solids, in addition to the repository growing dynamically, with each new pipeline executed I look forward to the new documentation!