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

My self-hosting infrastructure, fully automated

github.com

Post reply on HN
Print view View original

141–150 of 228 posts

Re: My self-hosting infrastructure, fully automated

#141

Post by nyellin »

dijit wrote: post #134
nyellin wrote: post #127

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 whi…

I don't know how you implemented it, but the big innovation of kubernetes was doing this with declarative inputs and using control loops for reconciliation instead of edge triggered changes.

It might not matter on a small scale, but on a large scale that's what makes it robust. It's also not trivial to implement a distributed version of this in house at scale. At the very least you need something like etcd at the core

Re: My self-hosting infrastructure, fully automated

#142

Post by rapnie »

kstenerud wrote: post #104

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…

> There are 19 stacks in this repository. 19 pieces of software that require their own maintenance, JUST TO RUN YOUR APPLICATIONS!

There's tools like Yunohost [0] that can save a lot of work and are focused on making the subsequent maintenance burden easier too. There's an application catalogue [1] with a lot of popular self-hosted apps to choose from and new ones being packaged all the time. I haven't used it myself yet, but hear very good experiences from people that have. Especially those that lack the more sysadmin tech skills and just wanna click-install & go.

There's also Freedombox [2]. I'd be interested to know about other such tools and your experience with them.

[0] https://yunohost.org

[1] https://yunohost.org/en/apps

[2] https://freedombox.org/

Re: My self-hosting infrastructure, fully automated

#143

Post by omnicognate »

rhizome wrote: post #59
simonw wrote: post #2

This is very cool! Have you considered something like Tailscale so you can securely access it from outside your home? I've been thinking about spinning up my own home server that way, seeing as Tailscale makes it easy to securely access it from my phone when I'm out and about.

Honest question: why not SSH?

The difference vs SSH for me (using plain Wireguard but achieving the same thing) is that I can set up my phone with always-on VPN to home and then wherever I am I'm effectively on my home network. I can access all my home-hosted services in my browser, securely access IOT things that can't talk to the open internet, use my home-hosted DNS rather than my mobile provider's, etc. I do use ssh over that connection (with Termux) to talk to servers, ofc.

Re: My self-hosting infrastructure, fully automated

#144

Post by [deleted] »

kstenerud wrote: post #104

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…

[deleted]

Re: My self-hosting infrastructure, fully automated

#145

Post by eloeffler »

tluyben2 wrote: post #111
kstenerud wrote: post #104

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…

I could post my fully automated self hosting infrastructure, but it would be boring. Few bash ssh scripts and LEPP stack. None of this complexity and yet 10+ years uptime. Interesting nonetheless but think i'll pass on this. I have done these setups at cloudproviders for clients; that is definitely the risk averse version; if something goes wrong every month with AWS, it's just 'ok'; if something goes wrong every 5 y…

> I could post my fully automated self hosting infrastructure, but it would be boring.

Actually, I would find that not boring :)

Re: My self-hosting infrastructure, fully automated

#146

Post by usrme »

rapnie wrote: post #142
kstenerud wrote: post #104

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…

> There are 19 stacks in this repository. 19 pieces of software that require their own maintenance, JUST TO RUN YOUR APPLICATIONS! There's tools like Yunohost [0] that can save a lot of work and are focused on making the subsequent maintenance burden easier too. There's an application catalogue [1] with a lot of popular self-hosted apps to choose from and new ones being packaged all the time. I haven't used it myself…

Thank you so much for name-dropping YunoHost! The demo alone sold me on finally going the self-host route for things such as ebooks, music, and photos.

Re: My self-hosting infrastructure, fully automated

#147

Post by BrandoElFollito »

input_sh wrote: post #106
cyfex wrote: post #102

I always found the hurdle with self-hosting to be maintaining, not the initial setup. Things like upgrading, in order to keep getting security fixes, and verifying everything works after the upgrade, are what has taken the most effort and time in the past for me. This looks like a great setup by the author, but difficult to maintain in the long run without significant time investment.

Docker and docker-compose make maintaining stuff dead simple to me. In like 95% of the cases it's just a matter of changing the version in a YAML file and running one command, and in the remaining 5% of the time I'm not concerned at all with some downtime because I'm (mostly) the only user.

This. I used to host directly on my server and discovered docker a few years ago.

It was a relief. Coupled with watchtower the updates are automatic except for the two services I really rely upon.

I used to be on Ubuntu for ages and moved to Arch a few days ago - my server only runs docker today.

I still want to keep access to a shell do it is Arch and not Rancher or something (I did not research much the bare metal hypervisors).

My maintenance is minutes every month if everything works fine, up to a max of an hour when Home Assistant broke things once two years ago.

DRP from bare metal is an hour.

Adding a service is a few minutes.

Re: My self-hosting infrastructure, fully automated

#148

Post by discardedrefuse »

candiddevmike wrote: post #44

I enjoy reading about homelabs that aren't using kubernetes or some other scheduler and how they're doing it/what the full stack looks like. This is just another "how I installed kubernetes" thing only without any real scale behind it. There are other ways to deploy and run things, and it takes people toying around with alternatives for something unique to spring up.

I'm currently building out my single-node "homelab" with coreos + podman + systemd. Most of the config is pulled from 1 ignition file during coreos installation. Its been a learning experience and but also very lightweight.

Re: My self-hosting infrastructure, fully automated

#149

Post by vimsee »

khuedoan wrote: post #47

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…

This looks very interesting. Already saved your github repo for later use. Also, overkill; what is that?

Re: My self-hosting infrastructure, fully automated

#150

Post by goodpoint »

Gigachad wrote: post #48
goodpoint wrote: post #13

Deploying services is 1% of the work. Maintaining them, fixing bugs and bottlenecks is the real works. And you cannot do when you deploy tools worth millions of lines of code. Complexity matters. Those popular products make sense only if you have a 20 engineers is your team or you don't care about reliability.

This is downvoted but I think it is true, self hosted services don't get nearly as much love as they need. It takes a huge amount of effort, monitoring, and knowledge on the specific tools to be able to host them securely and detect intrusions. I attempted self hosting for years but decided it ultimately wasn't worth it and that I have very little ability to prevent against attacks or detect that they had happened.

Not my point. Self-host plenty of stuff but choose *simple* tools, not behemots.

Also it's important to use software packaged in distros like Debian in order to receive security updates for many years.

Post reply on HN