

Well that’s easy to remember!
I do stuff


Well that’s easy to remember!


Conflicts haven’t been an issue for years, all modern iterations of KeePass (XC, kp2a, DX) support automatically merging in the latest before saving.
I’ve been using it for years this way across several devices, it’s incredibly solid


Store your database in a nextcloud instance and it’s that too


There’s also an app called Shutter that works quite well


I switch between this and Shutter on a regular basis depending on what I feel like using that day.


Most of the complaining I see is that they’re not going open source, they’re going “source available”


That just sounds like something a discord bot could do


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.
Oh man, thanks for this. I had no idea, having used gitea for years now.


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


Ok, sure. I recognize that not everyone has a computer. And sure, an F-droid release would be really helpful for those people, if “build it yourself” was the only way to get the app.
But … It’s not like the app is inaccessible. It’s on the play store. You can install it.
My main frustration is the outright demand for the project creator to “Just release it on F-Droid” - Something that requires the creator to get familiar with F-droid and do the extra leg-work to release it there. But … It’s an open source app, created for free by someone who wanted to create it. They owe you nothing. Not even “good distribution”.


I highly recommend the Dark Reader extension for your browser


Wow, the entitlement of “I don’t want to do things myself, do extra work for me instead”.


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.
I run my pi-hole on a dedicated Pi, and I pull the updated image first without any trouble. Then after the updated image is pulled, recreating the container only takes a few seconds.
Dunno what’s broken about your setup, but it definitely sounds like something unusual to me.