Live data from Hacker News

My self-hosting infrastructure, fully automated

github.com

131–140 of 228 posts

Re: My self-hosting infrastructure, fully automated

#131

This is definitely cool, but it also highlights a huge problem we have with software nowadays. There are 19 stacks in this repository. 19 pieces of software that require their own maintenance, JUST TO RUN YOUR APPLICATIONS! The amount of extra work required just to host the software that views your pictures, plays your videos, and allows chat with people is absolutely insane. I'm not talking about this particular rep…

It's not just running an app. He's building a setup that supports FANG-level infrastructure with autoscaling, self healing, etc.

Maybe it's unnecessary for tiny companies, but if you're dealing with infrastructure at scale then the complexity is unavoidable. The only question is whether you want to invent it in house or use a robust system that someone else built properly.

I elaborated more in my comment below

Re: My self-hosting infrastructure, fully automated

#132

Earlier quoted context omitted.

I've used everything under the sun and for homelab use IMO nothing beats using docker-compose and salt. 1. Unless you have crazy dynamic scaling needs, there's literally no point in using k8s or nomad 2. Unless you want RBAC and fine tuned ACL, theres literally no point in using k8s or Nomad I hate this idea that you need a Ceph cluster and a 3 node HA cluster to have a home lab. Not saying don't do it because you wa…

I also run everything with docker stack(s) currently. Not using salt and haven’t heard of it. Why would I want salt and not ansible or something similar?

Salt (https://saltproject.io/) was an almost-winner around the time that Ansible blew up. It's pretty irrelevant nowadays since terraform and kubernetes - but still it's a very very good tool.

I'd suggest if you already know Ansible then don't change. If you have no idea which is which then try them both and let us know :)

Re: My self-hosting infrastructure, fully automated

#133

How much energy does this consume? I have done some home lab going on over the years, and find that trying to do more on less W has been the most fun.

(Author here) Yep that's my goal too, hence the small form factor PCs. It costs me around 2-5$/month depending on how much I play with it.

Re: My self-hosting infrastructure, fully automated

#134

To everyone saying that Kubernetes is unnecessary, try implementing autoscaling, service discovery, secrets management, and autohealing in a vendor independent way without it. Of course none of that is necessary for a self hosted home lab, but neither is gitops. This is a very nice example of how to set stuff up properly. OP, I would love to see Robusta ( https://robusta.dev ) as part of this too. It's definitely in…

Oh. I’ve actually done that. It’s not as hard or complicated as you claim.

This was before kubernetes, arguably learning kubernetes is harder than implementing auto discovery and auto healing because you have to learn a lot about cluster semantics, the various network providers, service accounts, role based access control, integrations with secrets manager or the very disparate implementations of custom operators which may operate in your environment.

Kubernetes is a platform, I don’t doubt it solves a lot of problems. But it’s a complicated wee beastie, and I say that as a person who did it the easy way and used GKE on Google Cloud

Re: My self-hosting infrastructure, fully automated

#135
post #115

Repo owner here, I just created this account, I'm a long time HN lurker. I was surprised to find this on Hacker News, I wanted to wait until the stable release before posting on HN, but thank you for posting :) This project is still in alpha stage, but please feel free to critique; I'd appreciate it. Edit 1: After reading some of the comments, I want to clarify a few things: - Because it is currently in the alpha sta…

Thanks for the project! Once deployed, how do you keep everything up to date?

I'm currently bumping the versions manually (via a commit), but I plan to automate that with system upgrade controller [1] and Dependabot [2] (or similar)

[1]: https://github.com/rancher/system-upgrade-controller

[2]: https://github.com/dependabot

Re: My self-hosting infrastructure, fully automated

#136

Earlier quoted context omitted.

Apt install your lamp stack Deploy your files Cronjob to apt upgrade every night Why does that need a full team? Or more than 10 minutes every few years?

one does not simply "deploy"

tar -xvf of your git repository

Re: My self-hosting infrastructure, fully automated

#137
post #130

Earlier quoted context omitted.

Apt install your lamp stack Deploy your files Cronjob to apt upgrade every night Why does that need a full team? Or more than 10 minutes every few years?

Okay but what happens when you have a breaking change from one of your updates?

From a standard system upgrade? Never happened to me in 20 years. Between OS versions sure, once every few years spend 20 minutes building from scratch

If it did happen, same as if your machine caught fire. restore from your backup

Re: My self-hosting infrastructure, fully automated

#138

Earlier quoted context omitted.

I've used everything under the sun and for homelab use IMO nothing beats using docker-compose and salt. 1. Unless you have crazy dynamic scaling needs, there's literally no point in using k8s or nomad 2. Unless you want RBAC and fine tuned ACL, theres literally no point in using k8s or Nomad I hate this idea that you need a Ceph cluster and a 3 node HA cluster to have a home lab. Not saying don't do it because you wa…

I also run everything with docker stack(s) currently. Not using salt and haven’t heard of it. Why would I want salt and not ansible or something similar?

I used saltstack at a decent scale.

The reasons that I used it were because the agent (called “minion”) initiates a connection towards the master, which can be handy if you’re behind NAT- but it was interesting to us because incoming connections are easier to manage at scale than outgoing ones.

Another reason was that the windows support was much more mature (though not perfect) and our environment was mostly Windows servers.

That said, installing the minion agent was easy, much easier than enabling winrm.

If you have sunk significant time into ansible I wouldn’t recommend switching, but it’s definitely not dead as per the sibling comment, I personally found it more enjoyable and easier to work with once understood the DSL pattern and added a few custom modules, it’s very simple underneath.

Re: My self-hosting infrastructure, fully automated

#140
post #130

Earlier quoted context omitted.

Okay but what happens when you have a breaking change from one of your updates?

From a standard system upgrade? Never happened to me in 20 years. Between OS versions sure, once every few years spend 20 minutes building from scratch If it did happen, same as if your machine caught fire. restore from your backup

For me it's when a library my app uses gets an update then my app fails.
Post reply on HN