Static site hosting hurdles • Hacker News Board

Re: Static site hosting hurdles

#181

Post by laundermaf » Wed, Sep 07, 2022, 4:38 PM UTC

chubot wrote: post #64

laundermaf wrote: post #59

Earlier quoted context omitted.

> what's wrong with shared hosting? You answered that yourself: > It costs less than $10/month That’s a lot of dollars for a static website. There are a myriad of free options and there have been for years. Kinda disappointing that they weren’t mentioned. Anyone wanting to deploy a static website knows the big 4, completely free: Netlify, Vercel, CloudFlare Pages, GitHub Pages.

I prefer not to use free services because they're not sustainable, and they usually come with strings attached Remember I've been using this for 13 years, and if it keeps on working the same way, I'll use it for another 13 easily. (I've hosted multiple sites on it over the years) The current page claims it's $3.95 a month if you pay yearly: https://www.dreamhost.com/hosting/shared/ I thought mine was more like $8 but…

It’s static hosting. If they change their terms, it couldn’t be any easier to switch. I switched most of my Netlify sites to CloudFlare Pages in like 10 clicks each. The whole point of having a static file is that they’re super easy to manage.

Worst case scenario you pay a few cents to host on S3 and stick any free-range CDN on it.

I categorically refuse to use any non-static hosting for static content. Your shared hosting runs code and can be compromised, especially if you host multiple software/sites on it.

Re: Static site hosting hurdles

#182

Post by justsomehnguy » Thu, Sep 08, 2022, 9:50 AM UTC

jacooper wrote: post #129

justsomehnguy wrote: post #92

Earlier quoted context omitted.

I'm using Caddy with Docker labels auto-configuration. It's somewhat PITA to configure if you don't need a public cert, eg something for testing or not having a public A/AAAA record, but otherwise the automagik just works. The only negative moment is what Caddy container restarts when the dependent containers starts|restarts, so you briefly lose all connectivity to all sites behind Caddy. [0] https://github.com/lucas…

There are also security implications that the webserver has access to the socket directly.

> Each caddy docker proxy instance can be executed in one of the following modes.

> Server

> Acts as a proxy to your Docker resources. The server starts without any configuration, and will not serve anything until it is configured by a "controller".

> Server instances doesn't need access to Docker host socket and you can run it in manager or worker nodes.

This can be mitigated by running in the Controller mode

Re: Static site hosting hurdles

#183

Post by miragecraft » Fri, Sep 09, 2022, 10:49 PM UTC

l72 wrote: post #155

laundermaf wrote: post #59

Earlier quoted context omitted.

> what's wrong with shared hosting? You answered that yourself: > It costs less than $10/month That’s a lot of dollars for a static website. There are a myriad of free options and there have been for years. Kinda disappointing that they weren’t mentioned. Anyone wanting to deploy a static website knows the big 4, completely free: Netlify, Vercel, CloudFlare Pages, GitHub Pages.

Sure, that is a lot for hosting a single static site. But, that $10 essentially gives you unlimited sites, unlimited email hosting, SSL cert management, lots of storage, unlimited network, and much more…

It's never unlimited, the terms and conditions for shared hosting are specifically designed to prohibit use cases (ex. file storage not connected with a website) that generate excessive usage.

And if you somehow find a loophole you'll quickly become persona non grata.

As the saying goes, TANSTAAFL.