Ask HN: What's on your home server?

[1]. https://github.com/pi-hole/docker-pi-hole/

https://github.com/tailscale/tailscale/issues/3363

Performance proved to be an issue for SD cards though, when attempting to host nextcloud and postgres. I do what teh_klev is talking about and selected the fastest USB stick I could find, which was a Samsung FIT Plus 128 GB Type-A 300 MB/s USB 3.1 Flash Drive (MUF-128AB), and this gave me a huge speedup.

Unfortunately Jellyfin is not really fast enough on an rpi and I have no solution.

Proxmox and Kubernetes, Rook on top of that for storage. GitLab for manifest storage, ArgoCD for deployment, terraform for node management in proxmox. It's not fully redundant (two separate nodes) but storage is replicated (ZFS send/receive on proxmox, Ceph replication for Rook).

Primary stuff are things like AP management, file shares, prometheus, grafana, various interfaces with 'dumb' devices, just to collect data from them without having them connected to the internet, VPN for remote access, separate VPN for internet tunnelling when on foreign networks, media service for movies and series, downloaders, Cloudflare tunnels to expose services to the big bad internet without opening ports, TFTP services for network booting, pull through caches for OCI resources and some other package indices. Also an OpenFlow controller but that was more for fun than because I needed it, no longer used for actual switches.

Main benefit from all the IaC is easy creation/destruction of entire environments when testing out things without having to pay money to a public cloud.

Also have BSD based firewall(s) to do NAT, DNS, DHCP etc. but those aren't on a shared home server but rather on separate hardware.

Similar setup in leased hardware in a DC just to keep the knowledge for legacy setups in on-prem style cases fresh, and public cloud version as well (but that costs money so it's scaled down significantly)/

- A Mac Mini, a Pi 4 with SSD and 8GB RAM and a Pi 3B+ forming a "multi-room" Kubernetes cluster with the idea that sensors and automation for each room (that had one) could be run locally in that room, including wired sensors, all connected by Kafka running on one of the Pis; that way I could just plug in another sensor and the local pod would know what to do with it. I never found a reliable way to allow pods to use serial devices and such, so while it's been fun, shifting priorities mean I had to scale it down to just the Pi 4 running HASS, Zigbee2MQTT, Mosquitto, NodeRed, uStreamer and a simple homebrew TTS API based on espeak. It's all docker-compose now, since docker works a lot more reliable with devices. It's a real shame, kustomize/flux/k8s is so much nicer for robustness and easy configuring (a second, different instance of my stack is running elsewhere, so I need that) and monitoring, debugging, ... is way more convenient, but I need those sensors to work and I can't spend as much time fiddling with it as I previously did, so it's docker-compose and Ansible for now.

- A Pi 3 running OctoPrint; since made redundant as my 3D printer (Prusa Mini) got the ability print over LAN with the last update. The webcam I use to monitor it is now running via uStreamer on the Pi 4. It's going to become the brains for the Freenove Big Hexapod Robot kit I've been gifted last Christmas.

- A Pi Zero W running a large-ish e-ink display with weather data and things like that. Still around, terribly useful, I'd love to have a second (but possibly one that doesn't take seconds to refresh...)

- A Synology running a Prometheus/Grafana stack, a MySQL, a docker registry for the Kubernetes cluster, Gitea with all the manifests and flux config so I could rebuild the Kubernetes cluster without internet access. Also still around, but I'll get rid of some of the stuff running on there. Reducing its attack surface and such.

And I'm using Tailscale like everyone else these days.