Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Self-Hosting like it's 2025

kiranet.org

Post reply on HN
Print view View original

131–140 of 240 posts

Re: Self-Hosting like it's 2025

#131

Post by montroser »

mr_mitm wrote: post #114

This site redirects to localhost:1313. Is this some sort of April fool's joke that I'm not getting? $ curl https://kiranet.org/self-hosting-like-its-2025/ //localhost:1313/posts/self-hosting-like-its-2025/

Yeah... Is this performance art? Intentional or otherwise? It's a jungle out there on the Internet -- we should take self-hosting as an opportunity to _simplify_. It doesn't probably need to scale way up, and doesn't need to scale across many teams of people, so it's a good time to shed a few of those layers of abstraction and get back to basics.

Re: Self-Hosting like it's 2025

#132

Post by dismalpedigree »

Proxmox on a NUC. Separate RPI running HaProxy to route requests. Public 443 forwards to haproxy. All on separate vlan from home network. Router allows ssh across vlan for specific IPs. Ssh only available from the specific IPs. Some of the VPS on proxmox run Nebula protocol (like tailscale but self hosted) and there is a lighthouse on a $2 VPS. This allows me to access specific resources only from mesh network when away from home.

Re: Self-Hosting like it's 2025

#133

Post by UK-Al05 »

0xEF wrote: post #51

I love the idea of self-hosting, especially since I keep a number of very tiny websites/projects going at any given time, so resources would not really be too much of an issue for me. What stops me is security. I simply do not know enough about securing a self-hosted site on real hardware in my home and despite actively continuing to learn, it seems like the more I learn about it, the more questions I have. My identi…

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.

Re: Self-Hosting like it's 2025

#134

Post by swizzler »

hankchinaski wrote: post #9

The only thing that holds me back for self hosting is Postgres. Has anyone managed to get a rock solid Postgres setup self managed? Backups + tuning?

I was using straight filesystem backups for a while, but I knew they could be inconsistent. Since then, I've setup https://github.com/prodrigestivill/docker-postgres-backup-lo..., which regularly dumps a snapshot to the filesystem, which regular filesystem backups can consume. The README has restore examples, too

I haven't needed to tune selfhosted databases. They do fine for low load on cheap hardware from 10 years ago.

Re: Self-Hosting like it's 2025

#135

Post by finnlab »

k8sToGo wrote: post #124
mr_mitm wrote: post #114

This site redirects to localhost:1313. Is this some sort of April fool's joke that I'm not getting? $ curl https://kiranet.org/self-hosting-like-its-2025/ //localhost:1313/posts/self-hosting-like-its-2025/

Now it's suddenly returning 404

my bad, works now. Don't test in production...

Re: Self-Hosting like it's 2025

#136

Post by raphman »

Brian_K_White wrote: post #121
0xEF wrote: post #51

I love the idea of self-hosting, especially since I keep a number of very tiny websites/projects going at any given time, so resources would not really be too much of an issue for me. What stops me is security. I simply do not know enough about securing a self-hosted site on real hardware in my home and despite actively continuing to learn, it seems like the more I learn about it, the more questions I have. My identi…

A few days after a remark on hn, while the thread was still active, I received a mysterious package I didn't order from a weird drop shipping service where the original sender is unknown and undiscoverable to you the recipient. It didn't contain anything bad just a single surgical mask (during covid, common valueless item basically). The message was just that they could find my home address. It was a stupid message s…

Hmm, my first guess would have been that you have been a target of "brushing" [1]. In a Reddit thread from 2020 [2], multiple people mention that they received surgical masks they did not order.

[1] https://www.bbb.org/article/news-releases/20509-amazon-brush... [2] https://www.reddit.com/r/tulsa/comments/hpe8s1/just_got_a_su...

Re: Self-Hosting like it's 2025

#137

Post by aborsy »

Aachen wrote: post #91
aborsy wrote: post #75

I can self host many applications, but their security must be outsourced to a company. I don’t have time to keep on top of vulnerabilities. Cloudflare Tunnels is a step in the right direction, but it’s not end to end encrypted. The question is then, how to secure self hosted apps with minimal configuration, in a way that is almost bulletproof?

> security must be outsourced to a company. I don’t have time to keep on top of vulnerabilities. If the software you host constantly has vulnerabilities and something like apt install unattended-upgrades doesn't resolve them, maybe the software simply isn't fit for hosting no matter what team you put on it. That hired team might as well just spend some time making it secure rather than "keeping on top of vulnerabilit…

The concern is zero days. There are probably lots of easy zero days, patched across a host of software, once discovered in one.

The solution is a secure software in front. It could be Wireguard, but sometimes you don’t know your users or they don’t want to install anything.

Re: Self-Hosting like it's 2025

#138

Post by skydhash »

brulard wrote: post #25
jagermo wrote: post #18

i really like this software-centric approach, but I am a bit stuck when it comes to the hardware. Are there some sources around servers that don't suck up too much energy and are fairly quiet? What CPU is a good all-round solution?

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…

I use an old mac mini. The two times the fan has come up was with me building ffmpeg and transcoding my music library. I us it as a file server, music server, amd jellyfin. And trying stuff.

Re: Self-Hosting like it's 2025

#139

Post by alabastervlog »

seba_dos1 wrote: post #54
bauerd wrote: post #10

Last thing I need is Kubernetes at home

"apt-get install" tends to be enough once you stop chasing latest-and-greatest and start to appreciate things just running with low maintenance more.

I only host 3rd party daemons (nothing custom) and only on my local network (plus Tailscale) so Docker’s great for handling package management and init, since I get up-to-date versions of a far broader set of services than Debian or ubuntu’s repos, clean isolation for easy management, and init/restarts are even all free. Plus it naturally documents what I need to back up (any “mounted” directories)

Docker lets my OS be be boring (and lets me basically never touch it) while having up to date user-facing software. No “well, this new version fixes a bug that’s annoying me, but it’s not in Debian stable… do I risk a 3rd party back port repo screwing up my system or other services, or upgrade the whole OS just to get one newer package, which comes with similar risks?”

I just use shell scripts to launch the services, one script per service. Run the script once, forget about it until I want to upgrade it. Modify the version in the script, take the container down and destroy it (easily automated as part of the scripts, but I haven’t bothered), run the script. Done, forget about it again until next time.

Almost all the commands I run on my server are basic file management, docker stuff, or zfs commands. I could switch distros entirely and hardly even notice. Truly a boring OS.

Re: Self-Hosting like it's 2025

#140

Post by qskousen »

fm2606 wrote: post #92
_mitterpach wrote: post #80

Earlier quoted context omitted.

Maybe try running your services in docker, I don't know how difficult that would be to implement for you, but if you run it in containers you can get it to start up after an outage pretty reliably.

Yeah, that is a good idea and as I have been doing a little bit of studying Kubernetes I thought about that too (overkill for sure).

If you need a middle ground between docker and k8s, you might have a look at nomad. Definitely a learning curve, and I find the docs lacking, but easier to set up and maintain than k8s.
Post reply on HN