3 ms·
A full virtual server is pretty far down on the list of options I'd consider if I wanted to host-and-forget a little static website for more than a decade. Just
by lxgr 4y ago
A full virtual server is pretty far down on the list of options I'd consider if I wanted to host-and-forget a little static website for more than a decade. Just to name a few concerns with this approach:
A small VM needs to be periodically updated, both due to changing web standards (e.g. an old TLS version becoming deprecated) and to prevent it from becoming compromised; at some point, an OS upgrade will become necessary; the service provider might deprecate an old VM format and require a migration to something else entirely.
If the author already does all of that, sure, there won't be any or only very little incremental effort. But weren't we talking about the specific risk of the author losing interest (not financial, but in maintenance) in a small pet project?
Now just contrast all of that with uploading one or a handful of HTTP files to a new server and a bit of configuration at the hoster or your domain/DNS provider.
Static web hosters are also plenty and much more economical (in terms of money and server resources) than running your own web server, and for the reasons above, I wouldn't really consider them "less autonomous".