3 ms·

> Get a box somewhere, serve you static content Good luck having a VPS 'box' that has an uptime record of 10 years. I know through personal experience that yo

> Get a box somewhere, serve you static content Good luck having a VPS 'box' that has an uptime record of 10 years. I know through personal experience that your VPS instance will go down, no matter how much you try to mitigate that. There will be bots and bad actors either trying to DDOS it, or trying to brute force `/wp-admin`. You could go for some obscure CMS to try and thwart that, but you run the risk of having vulns in that software because it doesn't have the eyeballs of vanilla Wordpress. You could always go for the shared hosting approach but the caveat being: there is no guarantee the shared provider will provide 100% uptime either. (And it will go down at the worst possible moment, like during a HN hug of death) Your best bet is to have your content distributed and mirrored across multiple services such that any attempt to take it down is impossible. I would go into details about that, but due to op-sec reasons I won't. Tip: Plaster your content all over the web such that a removal of one piece of content does not affect the others.

dgellow 5y ago
You're moving the goalpost way further or have a completely different goal in mind than I do. The only thing that you need if you want to publish content online is an nginx config and a machine with a public internet access. And that's it. No CMS, no wordpress. Almost nobody has a need for 100% uptime so I don't see why you would mention that. If someone wants to DDOS you you have completely different situation and it is very likely your content will be offline, which is fine, no? It's costing them money and the only downside on your side is to not have your publications available for some amount of time. If you're talking about business services, sure, that's a big deal, but for a person sharing their writing, that's a non-issue. It takes what, something like 30 minutes to get another machine, setup nginx, then upload your content? A $5/month server with debian + nginx serving static content can survive way more than a HN hug of death.
influx 5y ago
It's pretty easy to serve static HTML out of S3, have auto renew set on your domain in Routet53, and good to go.

dgellow 5y ago

You're moving the goalpost way further or have a completely different goal in mind than I do. The only thing that you need if you want to publish content online is an nginx config and a machine with a public internet access. And that's it. No CMS, no wordpress. Almost nobody has a need for 100% uptime so I don't see why you would mention that. If someone wants to DDOS you you have completely different situation and it is very likely your content will be offline, which is fine, no? It's costing them money and the only downside on your side is to not have your publications available for some amount of time. If you're talking about business services, sure, that's a big deal, but for a person sharing their writing, that's a non-issue. It takes what, something like 30 minutes to get another machine, setup nginx, then upload your content? A $5/month server with debian + nginx serving static content can survive way more than a HN hug of death.

influx 5y ago

It's pretty easy to serve static HTML out of S3, have auto renew set on your domain in Routet53, and good to go.