Selfhosted

I didn't find anything for syncing yet. But I settled with plain smb shares which works for 99% of my needs and https://www.filestash.app/ for a simple webUI which is more convenient when browsing files and photos from the phone.

why not just NFS or smb in a tailscale network?

I did not know about opencloud.eu, and now I'm intrigued. I was always looking for a simple Google Drive alternative, but Nextcloud was too much. Will definitely keep an eye on it.

I was in the same boat... I just wanted a simple god damn self-hosted cloudStorage without any nitty gritty or all the bloat that comes with most local/self-hosted cloud solution...

Syncthing is good, but not really a cloud storage solution (I love syncthing and I use It to sync all my backups !!).

Give SFTPGo a try :) It also has a WebDAV functionality if you wan't to use it that way ! It just plain file storage with security features. However, not sure there are any application available, it mostly used it as web application :).

Check out MinIO. It's S3 compatible, so generally any tool which works with S3 will work with your instance. You can pair it with other FOSS applications like rclone. It's a great combo.

Seafile is ok. It has a weird docker container setup (multiple processes running in a single container) but works okayish

I don't know that I can answer your question, sorry, but something you said confuses me.

• file storage/syncing from a central server (so Syncthing is out) ... While working absolutely fine for sync between different devices (have it in use in a different scenario), the peer-to-peer nature is unsuitable for what I'm looking for

Why? I think you missed describing a requirement, because there's no reason SyncThing can't do "for syncing from a central server." Do you mean one-way, or one-to-many, or what? What, exactly, doesn't SyncThing do that you need?

I believe SyncThing is not the right tool in many scenarios, but I don't understand these bullet points.

For one thing, SyncThing is only peer-to-peer if you set it up that way. You can absolutely define a "master" simply by only connecting the "clients" to the master. It's an utterly arbitrary distinction, but the clients won't know about or communicate with each other unless you explicitly pair them with each other. This is how I have our phones set up: each one is paired to the central server, but neither is an introducer nor knows about each other. We have one directory that the server has shared with both phones, and several directories that the server shares only with one or the other phone. I even have the server connected and sharing all of the directories with a second, backup server that neither phone knows about.

Again, I'm not pimping SyncThing; it has weaknesses, the biggest one being any lack of sophisticated merge ability. I wish it had a plugin system where, for each for type, in case of conflicts it would call out to some external merge program; rather than just throwing up it's hands and going, "well shucks, guess I'll just spam a bunch of sync conflict files". And it can be annoyingly slow recognizing changes and syncing; it would be a terrible choice for any sort of pair programming file sharing.

But what problems have you encountered with it, for your case?

Maybe Karadav with the Nextcloud clients/apps.

Not sure if that will support selective sync, I don't see anything saying specifically no on the repo.

You should checkout Seafile again. It’s so easy and way faster than NC.