took a cut at refreshing the deployment docs!
requesting changes because i think we should drop the diagram
what if $DAGSTER_HOME isn't set
, launch Dagit as a ...
can we provide an example
we should emphasize that this is not in the instance yaml, and maybe add a phrase explaining that/why execution is configurable on a per-pipeline basis
you can also do this off aws
you'll probably also want to -- b/c everything should work fine with EBS as well
we went back and forth quite a bit on diagrams for this and while we don't have a final, accepted version, i think consensus was that some of the semantic slippages that are preserved in this version are misleading -- can we drop this?
let's explain why
i think this is a little inexact -- pipelines don't include config, etc.
this is confusing, we should use the words system storage
can we maintain the previous info as well
this is confusing to surface in a document at this level
added explicit setting of $DAGSTER_HOME above
hmm. I wasn't even going to mention this file here, since I think it's kind of a distraction, and I don't want the reader to rathole on a file that they probably won't ever have to touch (in 99% of regular use, I don't bother looking at it) - I could just remove this mention? Thoughts?
yeah, I agree. I still think this is super confusing (see https://github.com/dagster-io/dagster/issues/1973) - but at least for now I agree that we should clarify the distinction
yeah trying to focus on the straight-line path to getting things running vs. presenting diversity of options here, I think we can provide some good discussion of less common patterns in the reference section later
I'm going to just remove this sentence along with removing the diagram
good call - changed wording to "Any pipelines that are configured with this YAML"
yeah agree, I'm going to remove 3