Page MenuHomeElementl

Cross-reference ECS reference deployment
ClosedPublic

Authored by jordansanders on Jun 23 2021, 2:45 PM.

Details

Summary

This links back out to GitHub to show the full ECS reference deployment.
Alternatively, we could create a new deployment guide in our docs site
with the contents of the README.

I think the rest of the AWS content is otherwise worth keeping (the RDS
and S3 stuff) so I didn't want to replace it wholesale.

Test Plan

none

Diff Detail

Repository
R1 dagster
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

docs/content/deployment/guides/aws.mdx
16

Do we have strongly held opinions on where the technical directions for running the example should live (docs site, README, or both)? I tend to prefer it in the README and find some of our other back-references from READMEs to the docs site to be disruptive - but I'm happy to bias toward whatever we think provides our best possible docs experiences.

Is there a way to render our docs site directly from the README so the two can't fall out of sync and so we don't need one to merely be a cross-reference to the other?

Harbormaster returned this revision to the author for changes because remote builds failed.Jun 23 2021, 3:37 PM
Harbormaster failed remote builds in B32508: Diff 40043!
Harbormaster returned this revision to the author for changes because remote builds failed.Jun 23 2021, 5:52 PM
Harbormaster failed remote builds in B32524: Diff 40067!
dgibson added subscribers: yuhan, sashank.
dgibson added inline comments.
docs/content/deployment/guides/aws.mdx
16

@sashank or @yuhan may have opinions here, I do not

18

Not ECSRunLauncher yet right?

This revision is now accepted and ready to land.Jun 24 2021, 2:15 PM