Ask HN: What's on your home server?

I have a small K3S cluster of RPIs and a Synology NAS. I don't trust the RPIs to store any meaningful data so I use the NAS to store and backup everything. The cluster can request persistent volumes and they are automatically created and exposed via NFS by the NAS.

On the NAS, it's mostly storage services:

  - MinIO (S3 compatible)
  - Postgres
  - InfluxDB
  - Syncthing
  - Plex (NAS has hardware encoding)
  - Print/scan server
  - Cloud Sync to Backblaze

On the cluster, all the "compute" services:

  - Traefik and cert manager to expose the services with HTTPS, both on the NAS and the cluster
  - Accounting service to invoice clients
  - Mayan EDMS to store and process the documents of my LLC. It was a pain to setup but it offers OCR and an API to search document content.
  - Home Assistant and mosquitto that I just started using. I'm playing with ESPHome to integrate some CO2 sensors.

On the unusual things on my network:

  - A LaMetric time that I use to push my own notifications
  - A RPI connected to speakers that I use as a pulseaudio server when I want to put music (`pactl load-module module-tunnel-sink server=tcp:x.x.x.x`)
  - A RPI with a 64x64 led matrix from Adafruit that I want to use like an on-air sign.

What are you going to move to now that Gitpod has retired self hosting?

I just got a generous amount of credit in one big cloud provider from my job, so I decommissioned almost everything inside my house. The only thing still on prem is an Rpi1 running ADSB feeder software, connected to an home made cantenna.

Right now I'm using a Synology NAS and two Raspberry Pis.

The Pis host ddclient, Pi-hole + Gravity Sync, cloudflared and PiVPN (Wireguard). I'm also working on setting up Logstash + Filebeat but one of them needs to be formatted for it to work. As you might guess, its purpose is redundant DNS.

The NAS is running a bunch of different things. Portainer, Wireguard, Invidious, a DNS-over-HTTPs endpoint, ddclient, Kibana, and various instances of nginx hosting some of my sites.

I host ddclient and Wireguard in all my machines for redundancy - the bare minimum I need to maintain this setup remotely is being able to connect to my VPN, so keeping my dynamic DNS record up-to-date and having at least one VPN endpoint available is vital.

This year, I want to add more hosts (probably more Pis, and a few nVidia Jetson Nanos I have lying around) and some sort of service mesh to switch to Docker Swarm. Eventually, I might replace the NAS with a custom-built server - I want to do a backup of my Steam library, and I've found the NAS a bit lacking when it comes to virtual machines.

while it is obvious my comment was hyperbolic, the underlying sentiment still stands regardless. I can be charitable only so far, not complaining that the drivers don't make my color image perfect on a vinyl postcard, not even complaining that I need to realign the heads or whatever every other time I've got to use the printer, those can be mechanical issues and probably not their fault. I just want to print black and white on A4 and a color print every month or so.

But the consistent issues almost every single home printer I've used had with regards to connecting to computers, both wireless and wired is not reasonable. There's a plethora of other issues but that's more on a software in general than driver front so I'll leave them out of it.

All these problems on a windows machine by the way, surprisingly enough I've had less headache with printers on linux than windows. Maybe the lack of software layers to muddle shit helps here, who knows

> I don't think the driver programmers have much fun with their jobs, having to deal with seemingly greedy product requirements, and lots of variation in real world use (humidity, paper type, ink quality, yada yada).

That's a normal job, everyone has greedy product requirements outside of VC money pits. Also don't think their job in the capacities I complained about is very much mechanical at all, yeah it's very much I/O but that doesn't mean much.

>I'd like to think I am about an average programmer and I am reminded by my own actions everyday that I know nothing. I am constantly learning (and forgetting) new ideas every week.

people learn stuff and do their jobs, its not rocket science, nobody know everything nor can hold all the information in the world in their heads. As far as i'm aware printer connectivity isn't some CS open question, it's not a new field that needs exploring, it should've been explored by now. Yes of course drivers are a bit of a moving target regarding support for different architectures, but printers aren't the only things that need drivers and yet seem to be the only ones consistently having this issue ever since I can remember(maybe network cards as well?).