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

231–240 of 240 posts

Re: Self-Hosting like it's 2025

#231

Post by brulard »

ryandrake wrote: post #187
seba_dos1 wrote: post #54

Earlier quoted context omitted.

"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.

Same here. I've had the same setup for decades: A "homelab" server on my LAN for internal hobby projects and a $5 VPS for anything that requires public access. On either of these, I just install the software I need through the OS's package manager. If I need a web server, I install it. If I need ssh, I install it. If I need nfs, I install it. I've never seen any reason to jump into containers or orchestration or any…

I have very similar setup, with homelab and separate cheap VPS. In similar manner I have all the services installed directly on the OS but I'm starting to run into issues where I started to consider using docker. I run nginx with multiple (~10) node apps running through PM2. While this works ok-ish, I'm not happy that if for example one of my apps needs some packages installed, I need to do it for the whole server (ffmpeg, imageMagick, etc.). Other problem is that I can easily run into compatibility problems if I upgraded node.js for example. And if there was some vulnerability in some of the node_packages any of the projects use, the whole server is compromised. I think docker can be quite an easy solution to most of these problems.

Re: Self-Hosting like it's 2025

#232

Post by loughnane »

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…

Since my setup is for personal use I just use a VPN. My home router is running OPNsense and this setup wasn't too bad. I also pay my ISP for a static IP address.

https://docs.opnsense.org/manual/how-tos/wireguard-client.ht...

Then on my phone I just flick on the switch and can access all my home services. It's a smidge less convenient, but feels nice and secure.

Re: Self-Hosting like it's 2025

#233

Post by brulard »

crabmusket wrote: post #99
ValdikSS wrote: post #2

Nah, that doesn't look fun. Self-hosting in 2025 should look like Yunohost or Sandstorm.

I really like Sandstorm - it's a glimpse into an alternate world of how things could be.

I tried the demo, but I still don't get it. What is it? Is it supposed to be like a collection of productivity apps, like google docs/drive ? The demo worked poorly, I waited very long time for many interactions, some didn't work at all (like changing font on etherpad).

Re: Self-Hosting like it's 2025

#234

Post by ohgr »

brulard wrote: post #230
ohgr wrote: post #118

Earlier quoted context omitted.

If it wasn't for Kubernetes we'd need 1/3rd of our operations team. We're keeping unemployment down!

Is this a joke? I don't know much about Kubernetes, but I've heard from devops people it's quite helpful for bigger scale infrastructures.

Unfortunately no it's not a joke. It's really fine for big infrastructure companies, think Google etc. But a lot of people will design complicated shit due to architectural ignorance or to make their resume look good and this will result in Kubernetes looking like a good idea to run the resulting large amounts of complicated shit. Then you realise it's complicated and lots of people need to look after it which escalates the problem.

After a few years you work out that holy shit we now have 15 people looking after everything instead of the previous 4 people and pods are getting a few hits an hour. Every HTTP request ends up costing $100 and then you wonder why the fuck your company is totally screwed financially.

But all the people who designed it have left for consultancy jobs with Kubernetes on their resume and now you've got an army of people left to juggle the YAML while the CEO hammers his fist on the table saying CUT COSTS. Well you hired those feckin plums!

etc etc.

Lots of them are on here. People have no idea how to solve problems any more, just create new ones out of the old ones.

Re: Self-Hosting like it's 2025

#235

Post by BrandoElFollito »

Helmut10001 wrote: post #3

I tried portainer once, it looked nice and had a lot of features... for which I had no use. I always found `docker compose` much easier to use, it is often just an alias and a tab away, where for portainer I would have to open a browser tab and sometimes even touch my mouse! Otherwise good article. If you want to go rootless (which you should!), Podman is the way to go; but Docker works rootless too, with some modifi…

You will love dockge then.

I run it alongside portainer because exactly of the compose.yaml file I want to have control over

Re: Self-Hosting like it's 2025

#236

Post by megous »

nijave wrote: post #178
megous wrote: post #11

My peace of mind comes from my self hosting in 2025 looking the same as my self-hosting in 2005 (except a move to systemd). I haven't even re-installed my workstation OS since 2006 or so.

I'm glad I'm not configuring php-fpm and compiling PHP add-ons from source. Someone else can shove that in a tarball (Docker image) for me

I'm glad I don't have to deal with docker's bloat and networking to avoid writing a 8 line php-fpm config file. :)

Re: Self-Hosting like it's 2025

#237

Post by crabmusket »

brulard wrote: post #233
crabmusket wrote: post #99

Earlier quoted context omitted.

I really like Sandstorm - it's a glimpse into an alternate world of how things could be.

I tried the demo, but I still don't get it. What is it? Is it supposed to be like a collection of productivity apps, like google docs/drive ? The demo worked poorly, I waited very long time for many interactions, some didn't work at all (like changing font on etherpad).

I agree the current experience is sonewhat unpolished. The docs explain the vision best: https://sandstorm.org/how-it-works

Re: Self-Hosting like it's 2025

#239

Post by FloatArtifact »

nijave wrote: post #168
FloatArtifact wrote: post #76

Self-Hosting like it's 2025...uhhgg... Don't get me wrong I love some of the software suggested. However yet a another post that does not take backups as seriously as the rest of the self-hosting stack. Backups are stuck in 2013. We need plug and play backups for containers! No more roll your own with zfs datasets, back up data on the filesystem level (using sanoid/syncoid to manage snapshots or any other alternative…

Why not zfs snapshots? Besides using Hyper-V machine snapshots, that's been the easiest way, by far, for me. No need to worry about the 20 different proprietary tools that go with each piece of software. Each VM or container gets a data mount on a zvol. Containers go to OS mount and each OS has its own volume (so most VMs end up with 2 volumes attached)

Well, one argument not to use ZFS is simply the resources it takes. It eats up a lot of ram. Also I'm under the impression that one should never live-snapshot a database without risk of corruption.

Re: Self-Hosting like it's 2025

#240

Post by cenamus »

fm2606 wrote: post #194
cenamus wrote: post #148

Earlier quoted context omitted.

I suppose also no public IP on your home connection? Because since my new provider only provides cg-nat, I've been using a cheap server, but actually having the server at home would be nice.

Correct, there is no public IP address exposed to my home. Right now my "servers" are Dell micro i5s. I've have used RPI 3 and 4 in the past. My initial foray into self-hosting were actual servers. Too hot, too noisy and too expensive to run continuously for my needs, but I did learn a lot. I still do even with the micros and pis.

What do you use for your remote server? Because even a VPS seems kinda overkill, if all it's doing is some redirecting. I guess you could do TLS termination there aswell...
Post reply on HN