←back to thread

221 points finnlab | 1 comments | | HN request time: 0.2s | source
Show context
bauerd ◴[] No.43545430[source]
Last thing I need is Kubernetes at home
replies(11): >>43545448 #>>43545480 #>>43545584 #>>43545606 #>>43545610 #>>43545648 #>>43545656 #>>43545661 #>>43548737 #>>43550543 #>>43552457 #
seba_dos1 ◴[] No.43545656[source]
"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.
replies(3): >>43546157 #>>43546335 #>>43548554 #
ryandrake ◴[] No.43548554[source]
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 of that complex infrastructure. I know there are a lot of people very excited about adding all of that stuff into the mix, but I've never had a use case that prompted me to even consider it!
replies(1): >>43556121 #
1. brulard ◴[] No.43556121[source]
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.