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

181–190 of 228 posts

Re: My self-hosting infrastructure, fully automated

#181

Post by Macha »

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.

My setup I just have ansible deploy to a couple of hosts running Arch. Generally I just use OS packages and have ansible deploy appropriate configs then for some software where that's more hassle I use podman rootless containers. Such software includes e.g. Graylog, which wants particular versions of Elasticsearch and mongo, or postgres which requires a manual data migration for annual version upgrades

k8s and nomad are on my "maybe eventually later" list though.

Re: My self-hosting infrastructure, fully automated

#182

Post by Macha »

ryandrake wrote: post #170
marginalia_nu wrote: post #163

Earlier quoted context omitted.

My "homelab" is just debian stable, with a moratorium against containerization. Systemd keeps the services going. Updates are manual. It's a bit incredible how clean and easy such a set-up can be. Like there's almost nothing to say. It's extremely reliable and just keeps ticking. I actually did use to have a bunch of virtualization and kubernetes and crap, but got rid of it because it ate literally half the systems'…

Yea I think I missed the whole web-complexity bus and am probably out of touch, but I still don’t get the use case for docker and containers and kubernets and and orchestration and all that stuff, just for a simple home setup. I serve a tiny web site, email, backups, a NAS and a few other internet services for my family, and my “stack” is vanilla Debian Stable. Maybe I don’t know what I don’t know, but my setup works…

I want multiple conflicting versions of Elasticsearch on the same host. My OS packages are built to support a single deployment. I could manually setup users, config files, systemd services, etc. for the second deployment, or I could just run them in containers, which is the lower effort option

Re: My self-hosting infrastructure, fully automated

#184

Post by marginalia_nu »

Macha wrote: post #182
ryandrake wrote: post #170

Earlier quoted context omitted.

Yea I think I missed the whole web-complexity bus and am probably out of touch, but I still don’t get the use case for docker and containers and kubernets and and orchestration and all that stuff, just for a simple home setup. I serve a tiny web site, email, backups, a NAS and a few other internet services for my family, and my “stack” is vanilla Debian Stable. Maybe I don’t know what I don’t know, but my setup works…

I want multiple conflicting versions of Elasticsearch on the same host. My OS packages are built to support a single deployment. I could manually setup users, config files, systemd services, etc. for the second deployment, or I could just run them in containers, which is the lower effort option

> I want multiple conflicting versions of Elasticsearch on the same host

Why do you actually want this? Even having one ES is a bit of a smell that you're probably over-engineering things.

Re: My self-hosting infrastructure, fully automated

#185

Post by necovek »

midasuni wrote: post #120
necovek wrote: post #71

Earlier quoted context omitted.

Commands you use every day in the CLI? In your editor? I can trivially enter Emacs and modify Apache config when it breaks backwards compat between distribution upgrades, but when it's infrastructure as code...

I can’t think of a single time I’ve had an Apache config break with upgrades - other than having to recompile the webservice proxy module to change the case of the Upgrade header for a device that doesn’t work with the standards and is case sensitive (Major upgrades every couple of years break the binary compatibility)

I am pretty confident it broke for me between 12.04 and 14.04 Ubuntu releases, and I am pretty sure both were already in the 2.x series.

Most likely the change in NameVirtualHost behaviour as listed at https://httpd.apache.org/docs/2.4/upgrading.html, but there are a bunch of other changes too.

Re: My self-hosting infrastructure, fully automated

#186

Post by tksb »

smasher164 wrote: post #23
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.

This is how I currently manage my RPi NAS on NixOS: https://github.com/smasher164/nas . Exposing Home Assistant over it allows me to do things like turn my lights off when I'm away from home, without exposing stuff to the public internet. https://www.blog.akhil.cc/shelly-dimmer

I was just looking into doing something similar after realizing how little my RPi3B+ running only HomeAssistant was actually doing. I'd love to have PiHole and Shelly among others so maybe this route on a RPi4B is the way to go. Thanks for this!

Re: My self-hosting infrastructure, fully automated

#187

Post by Macha »

marginalia_nu wrote: post #184
Macha wrote: post #182

Earlier quoted context omitted.

I want multiple conflicting versions of Elasticsearch on the same host. My OS packages are built to support a single deployment. I could manually setup users, config files, systemd services, etc. for the second deployment, or I could just run them in containers, which is the lower effort option

> I want multiple conflicting versions of Elasticsearch on the same host Why do you actually want this? Even having one ES is a bit of a smell that you're probably over-engineering things.

Dependencies of software I didn't write (e.g. Graylog)

Re: My self-hosting infrastructure, fully automated

#188

Post by afeiszli »

khuedoan wrote: post #50
mcescalante wrote: post #21

Earlier quoted context omitted.

I just stumbled on a self hosted project similar to tailscale: https://github.com/gravitl/netmaker . There is also https://github.com/juanfont/headscale which is an open sourced implementation of the Tailscale coordination server. Tailscale "just works" and makes things incredibly easy for personal use, but it's awesome that there are also similar self-hosted options out there

(Repo owner here) I'm planning to build my own router with OpenWRT and install Wireguard on it, however due to the chip shortage I can't get the hardware for a reasonable price yet. Netmaker looks amazing, I need to play with it.

Netmaker repo owner here. Let us know if you have any questions and we can help out!

Re: My self-hosting infrastructure, fully automated

#189

Post by marginalia_nu »

Macha wrote: post #187
marginalia_nu wrote: post #184

Earlier quoted context omitted.

> I want multiple conflicting versions of Elasticsearch on the same host Why do you actually want this? Even having one ES is a bit of a smell that you're probably over-engineering things.

Dependencies of software I didn't write (e.g. Graylog)

This is what I'm getting at. That is an enormous overkill for a single server, and exactly the problem with kubernetes: It drives so much complexity that you kind of need this type of heavy-duty enterprise grade solutions even in an area where you really shouldn't need it.

If it's just a single server, you're fine with logrotate and grep.

Re: My self-hosting infrastructure, fully automated

#190

Post by naasking »

ryandrake wrote: post #170
marginalia_nu wrote: post #163

Earlier quoted context omitted.

My "homelab" is just debian stable, with a moratorium against containerization. Systemd keeps the services going. Updates are manual. It's a bit incredible how clean and easy such a set-up can be. Like there's almost nothing to say. It's extremely reliable and just keeps ticking. I actually did use to have a bunch of virtualization and kubernetes and crap, but got rid of it because it ate literally half the systems'…

Yea I think I missed the whole web-complexity bus and am probably out of touch, but I still don’t get the use case for docker and containers and kubernets and and orchestration and all that stuff, just for a simple home setup. I serve a tiny web site, email, backups, a NAS and a few other internet services for my family, and my “stack” is vanilla Debian Stable. Maybe I don’t know what I don’t know, but my setup works…

> but I still don’t get the use case for docker and containers and kubernets and and orchestration

For docker there's a simple motivating case: some services are difficult to configure securely with minimal permissions, and having a standard docker image provided by people who know what they're doing would be a big net win for security on the internet. There are a lot of poorly configured and insecure http server's out there. Think about how many vulnerable http servers are running on routers.

Post reply on HN