I’ve been running syncthing for a couple of years now and it does what it says on the tin quite well. One thing I’m missing is the ability to share files (e.g. a common Keepass database between myself and my wife) and maintain these synced. It appears that File Browser Quantum may support me here although I’m not sure I understand how. A.t.m., I have a folder on my laptop that is shared with a server and the server shares it to my mobile and my wife’s mobile. But if I try to share that folder with my wife’s account on my laptop (Debian), things get complicated. So maybe what I should do is use the folder on my laptop (my account) as the root folder for FBQ and then let FBQ sync it with my wifes devices and accounts? Just a bit worried that if I let both Syncthing and FBQ operate on the same folder, I may get conflicts arising. Anyone have similar use cases and what to share their experience? I’ve read of people using both these tools effectively.
VaultWarden with a shared account/password would work. You really can’t resolve conflicts in binary/encrypted files with Syncthing or anything.
I don’t understand why you want to introduce fqb, syncthing seems to be enough for your usecase ?
Not quite following you there, let me see if my system helps.
I have a NAS with multiple syncthing instances (services) running:
- me, my laptops, my phone
- my partner, their laptop & phone
- other equipment in the house (for Music, etc) For me & my partner, I added a shared folder that both syncthing instances used.
It works fine if you ignore file ownerships and set the underlying permissions so both users (ie the group
users) have write access. But, if we’re both editing something, syncthing will nuke one of them (so I have versioning on). But for us this never happens as they’re rarely writing to those files.Yes, I have exactly the same setup. But we’ve lost a couple of password because we had Keepass open at the same time. This never happened with Nextcloud.
There is no easy solution to this for your case, because you want versioning, not syncing. Versioning is what makes collaboration on google docs or o365 possible, with some merge logic to bring together non-colliding changes. Syncthing cannot do that beyond the granularity of individual files.
Syncthing works well when one of the sync members holds the “true” copy and everyone accepts changes one at a time.
Im having a hard time understanding the constellation of your current setup. From what i understand you have:
- You and your wifes phones
- A shared laptop with two accounts
- A server running FBQ and or syncthing?
The way i see it you could just use syncthing for all of these, no need for FBQ.
If you need FBQ though i dont think having a single folder synced by both FBQ and syncthing will cause any issues as long as they arent acting in parallel.So
device1 <syncthing> device2 <FBQ> device3should be fine,
butdevice1 <syncthing> device2 <FBQ + syncthing> device3might cause issues in my experience with doing the same with nextcloud.I have a setup where i use a nextcloud server that keeps file version history. Then i have a laptop that is connected to the server through nextcloud. That laptop then syncs that same nextcloud connected folder through syncthing to like ~10 other laptops. So basically all the laptops talk to each other to stay in sync through syncthing and then one of those laptops also uses the nextcloud app to sync this syncthing cluster to a nextcloud server for version control.
Almost there:
- You and your wifes phones -> YES
- A shared laptop with two accounts -> YES
- A server running FBQ and or syncthing? -> NO, currently only Syncthing but was considering FBQ to solve the sharing bit.
Although I think I get what you are saying. I think Syncthing can be setup to keep backup copies but not exactly the same as versioning I guess. Maybe I just have to go back to something more similar to Nextcloud but that is not Nextcloud like OwnCloud Infinite Scale or Opencloud.
Versioning is a whole other topic ofc, but just for syncing i dont quite get what the issue is?
One thing I’m missing is the ability to share files (e.g. a common Keepass database between myself and my wife) and maintain these synced.
This should be perfectly doable with your current syncthing-only setup no?
Or do you mean “share” as in to other people beside you and your wife by means of a public link?
Then you could do what i do and have your server run both syncthing and the web-cloud (whichever you choose) on the same folder. As long as you dont access the same file at the same time it should be fine and even if you do, syncthing will just keep a copy of the conflicting file and name it “.conflict_date…”. You might want to define an ignore pattern on the syncthing side though so it doesnt sync all the cloud specific metadata files to your personal devices.
