I’d stay on zfs, I simply don’t trust btrfs’ raid implementation. For very important documents I also set copies=2 (or 3) on that dataset, just in case.

And as others already said: 3-2-1 backups ;)

+1 for the letsencrypt wildcard with DNS verification, been using this for years. with dehydrated (https://github.com/dehydrated-io/dehydrated) you can automate renewing the certs, pretty convenient.

One thing i didn’t see mentioned yet - you can also easily create a wildcard for a subdomain of your domain, e.g. *.local.example.com. Most DNS providers let you define something like _acme-challenge.local IN TXT ... so you don’t even need to define an extra zone for local.example.com. Probably makes no big difference, but i like it ^^

I’m using https://github.com/dracut-crypt-ssh/dracut-crypt-ssh on some of my servers. The initrd opens an ssh port where you can login and enter the passphrase. Setting it up is non-trivial, but it works well. Haven’t tried it on Debian but there should be something similar.

Well, yes, but…

nextcloud forked owncloud back when there was only the php codebase.

opencloud forked owncloud ocis, which is a rewrite in go.

So while both forked “owncloud”, or “something named owncloud”, i doubt they’ll have any code in common.

Owncloud seems to be pretty much over IIRC.

The company behind it got bought be some american company in 2023, that promised that everything will “stay as open as it is” - you won’t believe what happened next ;)

Then recently many of the developers left to join OpenCloud, which seems to be a fork of owncloud, lead by a german open source veteran.

https://github.com/opencloud-eu