Quote:
Originally Posted by asdfasdf
The issue with BTSync seems to be a known limitation. One of the devs said they plan to implement it (force sync no - matter what file changes the peer makes it automatically gets resync'd to be the same as the main seed). But there is no ETA that I can see.
|
This seems to be implemented now with the latest version of BTSync. There is an option called 'overwrite changed files'. So it doesn't matter what my client peer/machines do, their Calibre library and db is always sync'd back to the main seed.
It is working very well now, fingers crossed. The other users in my household can browse my calibre library and copy books to their devices, their library always stays up to date and the db never gets screwed up.