←back to thread

DigitalOcean App Platform

(pages.news.digitalocean.com)
646 points digianarchist | 1 comments | | HN request time: 0.216s | source
1. dkersten ◴[] No.24699460[source]
I just tried it out with a Jekyll site I have running on Cloudflare Worker Sites. It detected everything and is deploying but one thing I noticed is that deployment is kinda slow. My GitHub Actions pipeline to build the Jekyll site and deploy to Cloudflare takes less than 2 minutes (latest run took 1m 43s). DigitalOcean took 6 minutes in comparison. Sure, its not crazy, but 3x the time still seems excessive.

It seems the bulk of the time was from installing ruby gems for Jekyll. Maybe GitHub Actions mirrors them or something so it can run faster?

Besides that, it works great. Actual live performance seems as snappy as one would expect from a static site and setting it up was almost one click. I'll definitely be looking into this in more detail.

First impressions are good and I may well migrate over for static site and API server (API server is currently running on a droplet as a single docker container, so seems like a nice way to lower the effort I have to put in). Everything else is running on AWS for.. reasons.. so this looks like a nice way to simplify my non-AWS stuff. I'll be experimenting with it over the coming days! The bandwidth limits are the biggest concern.