Hacker News Reader

Depends on the scenario really. If you want it version controlled, yeah sure. But there are other use cases that don't need that. You just want a "publishing target" that is low cost and minimal complexity. Plus GitHub/GitLab don't have the same number of availability-9's that Azure Blob Storage or AWS S3 can have.

View on HN

True but if you don't have a billing account set up then SCM can be easier. I usually stick CloudFlare in front of it for availability (with multiple entries for the origin in the DNS). You can even add a page rule to cache the HTML in case the server does go down.

Yeah I've done the Cloudflare + GitHub pattern as well for a couple things. But not everything is suited to that, nor needs that. Cloudflare also isn't going to cache large static content for very long or at all. Or just having any cache in between at all might be the wrong solution entirely. Anyway... :) S3 supports this and AzStorage doesn't - this needs fixing!

Have you heard of Surge (https://surge.sh)? Pretty nails the 'low cost and minimal complexity' target for static hosting, although I don't know how well it scales.

Reply on news.ycombinator.com