3 ms·

I switched from Vercel static site hosting, because I recently read an article here about how it's usually more economical to scale vertically instead of horizo

I switched from Vercel static site hosting, because I recently read an article here about how it's usually more economical to scale vertically instead of horizontally (i.e. use one big server for everything). Even though I'm only running a few services, I did the math and realized it's absolutely true. I can fit everything I'm running onto one DigitalOcean droplet behind Cloudflare for $24/month + an extra 25gb block storage for $2.5/month + $5/month for backblaze backups. Everything being: a bunch of static sites, Keycloak Auth, Rocket.Chat, Odoo business management software, Nginx Proxy Manager, Outline (self hosted Notion), Docker, Portainer, Cockpit, Listmonk. Static sites are free actually, besides storage. You can just add a location directive pointing to the folder in Nginx Proxy Manager and it'll serve the files for you. The biggest memory hog is Keycloak which is a Java app so it uses 700mb of ram. But in any case I have set up an entire small business software suite with a hosting cost of $31.5 and I can host unlimited static sites with no additional cost.

laundermaf 4y ago
The other problem is that one goes down, they all go down. A static website has absolutely no reason to go down.
- ipaddr 4y ago
  But often does because the host, external lib or cloudfaire has an issue.
- pdimitar 4y ago
  Hardly a problem for a personal blog. I host a few things on my baremetal server at home. When I get kernel updates (2-3 times a month) the Docker container with the Pi-Hole is rebooted and for 30 secs DNS resolution doesn't work in our home network. I probably can fix that by changing the script to do blue-green deployment (only stop the container after a new one has been brought up) but it honestly isn't such a problem. If it bothers me I will likely spend no more than one hour to fix it.
- esperent 4y ago
  It's all containerized. The only reason for it to go down is if DO or CF have an outage. Which is rare enough that it's not an issue for me.
nicbou 4y ago
There's a bit of risk to having all your eggs in one basket. One is security, although containers mitigate that. Another is resource allocation. If one piece of software hogs all the resources, others will suffer. Personally I split things just because it matches my mental model. My personal website runs somewhere. My professional website runs somewhere else. My home server gets its own dedicated hardware.

laundermaf 4y ago

The other problem is that one goes down, they all go down. A static website has absolutely no reason to go down.

ipaddr 4y ago
But often does because the host, external lib or cloudfaire has an issue.
pdimitar 4y ago
Hardly a problem for a personal blog. I host a few things on my baremetal server at home. When I get kernel updates (2-3 times a month) the Docker container with the Pi-Hole is rebooted and for 30 secs DNS resolution doesn't work in our home network. I probably can fix that by changing the script to do blue-green deployment (only stop the container after a new one has been brought up) but it honestly isn't such a problem. If it bothers me I will likely spend no more than one hour to fix it.
esperent 4y ago
It's all containerized. The only reason for it to go down is if DO or CF have an outage. Which is rare enough that it's not an issue for me.

nicbou 4y ago

There's a bit of risk to having all your eggs in one basket. One is security, although containers mitigate that. Another is resource allocation. If one piece of software hogs all the resources, others will suffer. Personally I split things just because it matches my mental model. My personal website runs somewhere. My professional website runs somewhere else. My home server gets its own dedicated hardware.