Open johnhidey opened 3 years ago
My strategy thus far been to mimic the structure of the DO API docs. So everything would go in an App
module. If you look at modules like ContainerRegistry
you can see what I'm talking about. Organizing by sub types (e.g. app deployment) would be too much maintenance overhead IMHO. I also think this approach makes it easier to grok this library with the DO API docs.
That works for me. I'll keep on working on getting the App
module finished. Hoping to find myself some time this weekend to work.
Thank you!
@anthonator , wanted to create an issue showing that DO apps is being added to the API. I started work on it but haven't gotten very far.
I'm thinking of breaking it down into multiple modules and wanted your take on it.
Not exactly sure where to put all the App Support calls like tiers, instance sizes, regions, app spec, and alerts. At first I was thinking of
App.Support
but not sure I like that.