Live data from Hacker News

Self-Hosting like it's 2025

kiranet.org

201–210 of 240 posts

Re: Self-Hosting like it's 2025

#201
post #154
post #108

Earlier quoted context omitted.

Don't expose anything to the Internet. Use a tunneling tool (Tailscale et al) or VPN

You'll have a hard time hosting websites/projects meant for the public to view, if you don't allow public internet traffic :)

We've been running production traffic via Cloudflare Tunnels for over a year with no problems. Ngrok and tailscale both run similar services, too.

Re: Self-Hosting like it's 2025

#202
post #65
post #25

Earlier quoted context omitted.

Depends on your needs. For some Raspberry Pi (ideally with 8-16GB RAM) + SSD can be enough if you are after low power consumption. If you need more power: I had success with HP ProDesk Mini (or any other one-litre PC), you can get these second hand from like $150 and extend RAM and SSDs however you like. You can even pick processor / generation to fit your needs best. These can have consumption from like 30W if I'm n…

> For some Raspberry Pi (ideally with 8-16GB RAM) + SSD can be enough Wut? For many, a Raspberry Pi with 1 GB RAM and the regular sdcard can be enough, you really don't need to go fancy if you don't want to run anything particularly heavy. Or if it's cpu-intensive then you might need the newest Pi or something even beefier but still only the lowest RAM and smallest/slowest storage options (like for WordPress). As you…

I don't know. I had run into problems building some packages for node and builing another tools with Cargo (i think) with 4 GB RAM. And if you going to experiment with containers, etc. I would definitely recommend starting at least at 8GB for a peace of mind. It doesn't cost a kidney nowadays.

Re: Self-Hosting like it's 2025

#203
post #10

Last thing I need is Kubernetes at home

I clicked expecting a list of cool things to self host. Instead I got a list of ways I would never want to host. Mankind invented BSD jails so that I do not have to tie myself in a knot of container tooling and abstraction.

Re: Self-Hosting like it's 2025

#204

Still running everything from my basement using FreeBSD jails and shell scripts. Sacrificing some convenience? Probably. But POSIX shell and coreutils is the last truly stable interface. After ~12 years of doing this I got sick of tool churn.

Not just stable - also easy to understand when, if ever, something goes wrong. There's very little magic, very little layers of complexity.

Re: Self-Hosting like it's 2025

#205
post #10

Last thing I need is Kubernetes at home

I clicked expecting a list of cool things to self host. Instead I got a list of ways I would never want to host. Mankind invented BSD jails so that I do not have to tie myself in a knot of container tooling and abstraction.

Indeed. I run a setup as you mentioned, with the various daemons in their own jail. Super simple set up, easy to maintain.

Lord knows why people overcomplicate things with docker/kubernetes/etc.

Re: Self-Hosting like it's 2025

#206
post #201
post #154

Earlier quoted context omitted.

You'll have a hard time hosting websites/projects meant for the public to view, if you don't allow public internet traffic :)

We've been running production traffic via Cloudflare Tunnels for over a year with no problems. Ngrok and tailscale both run similar services, too.

There is also https://pinggy.io which is even simpler to use. Just paste one command like ssh -p 443 -R0:localhost:8000 qr@a.pinggy.io

Re: Self-Hosting like it's 2025

#207

Still running everything from my basement using FreeBSD jails and shell scripts. Sacrificing some convenience? Probably. But POSIX shell and coreutils is the last truly stable interface. After ~12 years of doing this I got sick of tool churn.

Same. Why add the complexity of docker/kubernetes/?

FreeBSD and jails is so easy to maintain its unbelievable.

Re: Self-Hosting like it's 2025

#208
This article motivated me to upgrade my hosting approach.

I've been running a DigitalOcean VPS for years hosting my personal projects. These include a static website, n8n workflows, and Umami analytics. I used manual Docker container management, Nginx, and manual Let's Encrypt certificate renewals. I was too lazy even to set up certbot.

I've migrated to a Portainer + Caddy setup. Now I have a UI for container management and automatic SSL certificate handling. It took about two hours.

Thanks for bringing me to 2025!

Re: Self-Hosting like it's 2025

#210

Earlier quoted context omitted.

Isn't 95% of it just blocking every port except the service you want to expose, and then making sure everything is up to date and the service is built in a secure way. WAF's etc just hide the fact the code in your service is full of holes.

What's the 5% that's not blocking ports for services you want to expose? Ensuring your infra is built in a secure way is as important as ensuring your service is built in a secure way.

Part of it is that you may get (D)DoSed and then your ISP may be any amount of pissed at you for taking on significant ingress traffic on a residential network.
Post reply on HN