Recently I often cannot deploy anything to them due to api.digitalocean.com (proxied by Cloudflare) responding[1] with HTTP 504 and HTML page. When API works, you may find yourself unable to provision new VMs or scale for 10 hours[2].

[1] https://status.digitalocean.com/incidents/cq52yzt3x3vw

[2] https://status.digitalocean.com/incidents/n10hm09yvq6y

I really like this. I run my site on a Digital Ocean app that's connected to Github. It's entirely static written in plain html + css but it's so nice to not be managing a server on the backend.

This is cool. I’ve been running a few personal projects on Glitch for the past year, and some have grown up enough I’d like to have them run on a more robust platform. Going to give this a try.

This is pretty cool. I wonder if they are deploying the app container directly to DO from your running Glitch app, or if there’s a build step?

Nice to a see a friend of the family. :) There's a build step we take care of in the background, so that we can use git as the underpinnings instead of anything proprietary. (The logs on a project show you all the stuff that's happening under the hood.)

Hmm, how does this work ?

For example, my requirement is

- I need Redis as the cache

- I need a cron system to run my cron job

- I need also a PostgreSQL database

Any guide for this kind of deployment to DigitalOcean with this ?

That was also my initial thought. I thought it would be similar to Heroku or Hatchbox. But I see there are lots of information missing on how to deploy a Rails or Django app with databases and redis etc.

App platform documentation is severely lacking.

"Open a digital ocean account, and get $100"

They don't mention it is valid for 60 days. I hate such Shenanigans! :(

are there things you're running into with the deploy-to-fastly option that technically necessitated a 'traditional' container-on-vm approach?

Nope! The goal here was just more options & more connections for devs to platforms they like and use. We plan to keep expanding on this kind of stuff.