Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I’m having some trouble getting the App Platform to recognize the format of my .do/deploy.template.yaml file. My in-progress template lives here.
While a deployed app’s spec seems to have all the resources (envs, services, databases, etc.) at the top-level, the “template” file requires that they be nested beneath a root spec key. This much makes sense (I guess?), but as far as I can tell, the setup wizard doesn’t really acknowledge anything within it.
It automatically detects the right type of application, but doesn’t pick up any additional Components, the declared databases, or prompt for the global envs I’ve defined.
The app spec reference is clear, but the deploy button how-to doesn’t quite fill in the gaps—or more to the point, doesn’t offer any more advice on how to deploy templates that define more than just a web Component.
Furthermore, the doctl apps spec validate .do/deploy.template.yaml appears to only support live schema, not the template structure, nor does it confirm what Components would be created.
Any help or (complex) examples is appreciated!
dolphinnn
Vaishnavi Vundyala
016512ea60864da0867e5280f293de
Peter Monadjemi
Prince7hakur
devjk1
fc9acbfbc3124cbf8df28a1c5c5cdb
ab871885551143798f41908c709271
gouskova
Saivion Services
Marin
182d09356ab94d3893ddfaca4f0270