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.

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 13 hours ago (3 children)

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.

  • source
  • hideshow 3 child comments
  • [–] [S] 1 point 13 hours ago (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 4 hours ago

    But do you have File Versioning setup on all the syncthing end points?

    If so, you'll at least get sync-conflict copies - yes, you'll still need to fix them, but at least they won't (shouldn't) be totally lost.

    I guess another idea is to have separate personal keepass files to help reduce the editing on a common file...? (That's what we have)

  • source
  • parent
  • [–] 1 point 9 hours ago

    Pretty sure KeepassXC keeps its DB closed unless editing, I've not had trouble syncthinging it to my phone. That said, if I was worried, I'd designate a network accessible DB as 'the truth' and have everyone edit that, then set up a systemd service using a rsync (guts of syncthing) script to put it on all the sometimes network inaccessible endpoints on a regular basis, daily maybe?

  • source
  • parent