Meanwhile, for my homelab I just use split DNS and a (properly registered+set up) .house domain - But that’s because I have services that I want to have working with one name both inside and outside of my network

Yep, as someone who just recently setup a hyperconverged mini proxmox cluster running ceph for a kubernetes cluster atop it, storage is hard to do right. Wasn’t until after I migrated my minor services to the new cluster that I realized that ceph’s rbd csi can’t be used by multiple pods at once, so having replicas of something like Nextcloud means I’ll have to use object storage instead of block storage. I mean. I can do that, I just don’t want to lol. It also heavily complicates installing apps into Nextcloud.

Certbot also does DNS challenge, fwiw

DNS challenge makes it even easier, since you don’t have to go through the process of transferring it yourself

Others have addressed the root and trust questions, so I thought I’d mention the “mess” question:

Even the messiest bowl of ravioli is easier to untangle than a bowl of spaghetti.

The mounts/networks/rules and such aren’t “mess”, they are isolation. They’re commoditization. They’re abstraction - Ways to tell whatever is running in the container what it wants to hear, so that you can treat the container as a “black box” that solves the problem you want solved.

Think of Docker containers less like pets and more like cattle, and it very quickly justifies a lot of that stuff because it makes the container disposable, even if the data it’s handling isn’t.

Ah, neat! I just looked it up and it does look useful.

I’ve never really had any trouble with dark reader speed-wise - though it gives one major bonus that no other extension has so far: Attempting to match the appearance of darkened websites to my system theme (Catppuccin)

I can’t tell if you’re agreeing with me, disagreeing with me, or suggesting some alternative

I highly recommend the Dark Reader extension for your browser

The solution for me is that I run Nextcloud on a Kubernetes cluster and pin a container version. Then every few months I update that version in my deployment yaml to the latest one I want to run, and run kubectl apply -f nextcloud.yml and it just does its thing. Never given me any real trouble.

Tailscale is an overlay network, like a traditional VPN, but with very little config needed to get everything connected. You can use their managed lighthouse and management servers or run your own with Headscale.

Basically you just login to tailscale on all your devices and they get a LAN connection piped over the Internet without opening ports or needing to manage any infrastructure.

Yeah that’s abysmal, but it’s a result of the fact that docsis has always been an asymmetrical standard in which upload speeds are lower than download. I recently moved house and my old ISP was fiber to prem, we had symmetrical gigabit. New house is cable ISP that only offers 1000/50… While docsis 3.0 supports up to 200mbps up. Bunch of greedy bastards.

They’re just preparing for one day when you have your own personal swarm of nano bots

Holy cow, 120 gigs in a database?

Also remember, you don’t want a backup solution, you want a restoration solution :-)

No worries

http* status code*?

If running php, I usually go with PHP-FPM and nginx, much faster than Apache in most cases

Tailscale basically uses NAT hole-punching, doesn’t require any port-forwarding ever, it’s great