Philip Jägenstedt

The most elaborate redirect rules are in https://github.com/whatwg/misc-server/blob/master/debian/marquee/nginx/sites/whatwg.org.conf.

Yes, of course, any solution that doesn't give full control of the URL layout I'd just rule out :)

Numbers in https://github.com/whatwg/meta/issues/161#issuecomment-598046081 suggest that everything would easily fit in a Git repo, but you can't serve a website from a repo so that doesn't solve everything here.

Hijacking this issue to drop some notes about using a CDN, which isn't the same problem as running out of disk space... Some numbers based on using `goaccess` to analyze...

It looks like https://www.digitalocean.com/products/app-platform/ could be something to look into for this. From a cursory view, it seems more like AppEngine, in that it supports Node.js and other languages, static...

I have looked into using DigitalOcean spaces with nginx in front, using `proxy_pass` to forward requests. This would allow us to keep all the redirects, which is nice. The main...

Hmm, I hadn't consider just using AWS S3, but that would probably solve most of this. What's not great about it is that we'd depend on *both* DigitialOcean and S3...

If we could put objects in the bucket which the nginx front end turns into a redirect to add a slash, then I think we'd be set. (We'd also need...

https://github.com/aws-samples/amazon-cloudfront-secure-static-site looks fairly promising for this.

I won't be able to make time from WHATWG infra work this year, so here's a brain dump. The /var/www/html.spec.whatwg.org/ directory on marquee is 29 GB, that's the biggest problem...