I'm a bit surprised to see this on the Hacker News frontpage. It's not terrible, but it's kind of just some how-to content on what I think many would consider a

I'm a bit surprised to see this on the Hacker News frontpage. It's not terrible, but it's kind of just some how-to content on what I think many would consider a fairly mundane task. On one hand, it IS a reasonable step up from SEO crap you'd read typing hot keywords like "React" and "Docker" into Google: it's relatively succinct and doesn't seem like it's doing anything wrong. On the other hand, it doesn't really build a case for why you'd do this, what the pros and cons of an approach like this is, etc. which is what I expect more people would find interesting. Like, for example, why would you do this? It's a good question for someone who's looking to do this to ask themselves before doing it, and therefore a good question to try to answer. Like for example, if I'm trying to deploy to a service like Fly.io or into a Kubernetes cluster, then this may very well be the right thing to do. However, if I'm a n00b and I just know people deploy things with Docker, I might miss that it'd actually be much easier to just push this stuff to Cloudflare Pages, Vercel, Netlify or another static pages hosting tool/CDN. Some people read articles like this without having much of a basis for why you would want to add all of this complexity, and it leads them to think it's the right choice when it isn't necessarily. Generally the answer for why to do this, in my mind, is something along the lines of uniformity; having everything be an OCI image is convenient, and in the case of a PaaS or existing container cluster setup, it might be necessary if you want your frontend deployment to go alongside your other containers. It also has the benefit of being easier to test exactly how it will run locally, whereas with something like Cloudflare Pages you might need to play around to figure out how things like redirect rules will wind up working when you actually deploy it.