farcaller

joined 1 year ago
[–] farcaller@fstab.sh 17 points 4 months ago (14 children)

I remember when minio just started and it was small and easy to run. Nowadays, it's a full-blown enterprise product, though, full of features you’ll never care about in a homelab eating on your cpu and ram.

Garage is small and easy to run. I’ve been toying with it for several months and I’m more than happy with its simple API and tiny footprint. I even run my (static html) blog off it because it's just easier to deploy it to a S3-compatible API.

[–] farcaller@fstab.sh 6 points 4 months ago

Specifically, use home.arpa, if you must use a private domain.

[–] farcaller@fstab.sh 1 points 4 months ago (1 children)

FWIW that java app isn’t much memory hungry and it's not cpu-intensive at all. There are no issues with running java apps at all if you spend 5 minutes figuring the basix flags on how to set the memory limits or run it in a memory-limited cgroup via some containers runtime.

[–] farcaller@fstab.sh 9 points 5 months ago (1 children)

I run k3s in my homelab as a single node cluster. I’m very familiar with kubernetes in general, so it's just easier for me to reason with a control plane.

Some of the benefits I find useful:

  • ArgoCD set to fire and forget will automatically update software versions as they happen. I use nix to lower the burden of maintaining my chart forks. Sometimes they break, but
  • VictoriaMetrics easily collects all the metrics from everything in the cluster with very little manual tinkering, so I am notified when things break, and
  • zfs-localpv provides in-cluster management for data snapshots, so when things do break I can easily roll back to a known good state.

k3s is, of course, a memory hog, I'd estimate it and cilium (my CNS of choice) eat up about 2Gb ram and a bit under one core. It's something you can tune to some extent, though. But then, I can easily do pod routing via VPN and create services that will automatically get a public IP from my endless IPv6 pool and get that address assigned a DNS name in like 10 lines of Yaml.

[–] farcaller@fstab.sh 8 points 5 months ago

IIRC they demonstrated an interaction with Siri where it asks the user for consent before enriching the data through chatgpt. So yeah, that seems to mean your data is sent out (if you consent).

[–] farcaller@fstab.sh 25 points 5 months ago (10 children)

If you drop the projector, then airpods already do it better when paired with the watch. There's no point in such a device at all, then.

[–] farcaller@fstab.sh 4 points 5 months ago (1 children)

Is there anything interesting at all reported in /proc/spl/kstat/zfs/dbgmsg?

[–] farcaller@fstab.sh 1 points 5 months ago

I did ran out of pcie, yeah :-( the network peaks at about 26gbit/s, which is the most you can squeeze out of pcie 3.0 x4. I could move the nvmes off the pcie 4.0 x16 (I have two m2 slots on the motherboard itself), but I planned to expand the nvme storage to 4x SSDs and I’m out of the pci lanes on the other end of the fiber either way (that box has all x16 going to the gpu)

[–] farcaller@fstab.sh 4 points 5 months ago (2 children)

I run 3900X with a 40Gbit fiber, packed with HDDs and nvmes. The box fluctuates around 90-110W use.

[–] farcaller@fstab.sh 2 points 5 months ago (1 children)

when you said that Nextcloud might not meet your needs, was your concern specifically the server-side data format?

I'd prefer them as plain files. Technically it doesn’t matter much to me if it's a database, if I have to spin up an S3-compatible API, or if I need to slice up a zvol for it, but I just prefer the files because then I can do zfs snapshots (in which I trust) and backup with restic (in which I trust)

[–] farcaller@fstab.sh 2 points 5 months ago

That gives me hope, thanks. I’ll try it, then.

[–] farcaller@fstab.sh 1 points 5 months ago

Lots of files. I'd offload old projects that I worked on with synology drive so they aren’t stored locally, only remotely (but are easily accessible).

view more: ‹ prev next ›