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.

  • trilobite@lemmy.mlOPEnglish
    2·
    1 day ago

    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.

    • unexposedhazard@discuss.tchncs.deEnglish
      1·
      23 hours ago

      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.