I have been using Syncthing on all of my machines and mobile devices for a long time. I honestly couldn’t image live without it these days, so thanks for that
I work in video post production and I’m trying to ascertain the risks in using Syncthing to sync a disk database between a number of machines. The purpose of this is for me to potentially work on the same project as my colleague, sat next to me on another machine. I’m not 100% sure whether the dangers they are warning me of are applicable in this scenario. I am also aware they would rather I use one of their paid solutions in the form of a postgres database.
This is the response I received from one of their staff:
"It’s an issue with concurrency.
If a Disk database is in use, but is being locked or written to by another application, there are no guarantees for sanity of the underlying data. Even if that other application is another DaVinci Resolve in another (or same) machine. This applies for DropBox, mapped drives, local rsync services, SMB shares and pretty much anything else you can imagine doing this.
The PostgreSQL server manages this concurrency well - it reports to the user if a project is already in use (and who is using it), it reports if a project is capable of collaboration and which bits are being used by which collaborators.
Disk databases are not designed for concurrency. If you wanna explicitly close projects in a database, ensure that whatever sync tool you have has finished syncing and access them from a different machine, we don’t expect that to cause issues… bar the risk you assume of the sync tool finishing its job correctly."
So I guess what I want to understand is, how does Syncthing deal with the synchronisation of files that are in use? Are their concerns valid, or is Syncthing a good fit for what I am trying to do?