You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The repo would showcase difference use cases with explanations of how/why something is done. The Runway docs can then link to these examples/use case docs.
Stacker has something like this that they use for example blueprints. At a minimum we should fork this.
I created a GitHub organization (runway-examples) that can be used for this to provided a dedicated scope for multiple example repos (similar to aws-samples)
The text was updated successfully, but these errors were encountered:
I have some bikeshed color thoughts on this, but the most significant is that we should probably not fork any of the existing stacker-blueprints and instead focus on integration examples & best practices we want to illustrate.
we should probably not fork any of the existing stacker-blueprints
I agree, this is worst case/least effort.
focus on integration examples & best practices we want to illustrate
Exactly. The fine details can be hammered out over time, this is to just get the ball rolling to start defining what it should be.
I would also like to see all of our samples & quick starts moved into dedicated repos with full, self contained testing. gen-sample would then clone the selected repo to provide a fully functional GitOps boilerplate.
The repo would showcase difference use cases with explanations of how/why something is done. The Runway docs can then link to these examples/use case docs.
Stacker has something like this that they use for example blueprints. At a minimum we should fork this.
I created a GitHub organization (runway-examples) that can be used for this to provided a dedicated scope for multiple example repos (similar to aws-samples)
The text was updated successfully, but these errors were encountered: