I’ve considered using v6 as I host a lot of services from my homelab and it would be great if each had its own address. The question I have is, is v6 prevalent enough that all the clients out there are ready to go and I can just switch my lab servers to v6 and swap my A records with AAAA records, or will I still need to serve up v4 (and therefore, may as well just stick with the topology, reverse proxies, etc. I’ve already got.)

If you do make a switch to Proxmox, then Proxmox Backup Server is where it’s at for backups. Its de-duplication feature is incredible. I backup all my Proxmox VMs/LXCs with it, as well as my non-Proxmox hosts (laptop, etc.), with proxmox-backup-client.

Personally, I’m using a few of those tiny Beelink PCs (a couple Mini S12 and an EQ12) with the N100 processor, as well as a couple larger rackmount PCs I built for situations where I needed to add an HBA or some other PCI-Ex device. I do recommend something like a Beelink before building, though - they run Proxmox fine, they’re inexpensive, efficient, quiet, and each one can run a handful of VMs.

Hummingbirds. I put a feeder out and I’ve been staring at that thing for days waiting to see a hummingbird.

I tried Grocy for a while, but eventually stopped. Data entry was a huge pain.

Using the iOS companion app to scan grocery items into the app resulted in data issues that prevented me updating the item in the web app later. The only recourse was to add the items by hand in the web app, but then go in to each one separately with the mobile app to register the barcode. This also resulted in losing the additional metadata about the products that the mobile app would automatically configure if you onboarded the items through the mobile app, as it was able to look up additional data online and prefill a lot of stuff.

At the end of the day, it was too much of a hassle. I do like the idea, and may come back to Grocy again, but for now I have to pass.

Mostly nothing, except for Home Assistant, which seems to shit the bed every few months. My other services are Docker containers or Proxmox LXCs that just work.

You didn’t happen to change an unprivileged container to privileged, or vice versa, after creating it, right? Doing so can break filesystem permissions, which could have resulted in something like this.

There are two kinds of datacenter admins, those who aren’t using VMWare, and those who are migrating away from VMWare.

A garbage article citing garbage sources.

All the *arrs are in the same Github repo.

It’s not as relevant today as it used to be, that’s for sure. Originally it was to limit transcoding of 4K content (which used to be a lot harder), and also to avoid the HDR tone mapping issues with 4K content during transcoding, both of which are largely resolved with newer hardware and Plex software updates.

The only reason I keep them separated now is because most of the folks I share with can’t direct stream 4K content anyway, and so I only share out the 1080p libraries in Plex. It keeps bandwidth usage down and limits having to go to hardware transcoding, which can reduce quality and introduces startup delays. The library I use locally indexes both the 1080p and 4K content, so Plex will always prefer the 4K if it’s there.

If diskspace ever became an issue, I’d probably consider merging the libraries again.

I do wish I didn’t need to run a second Radarr instance to have both 1080p and 4K media.