New option: force "resync" to revert the modifications on clients

Hello team,
We start using seafile for a long time and users are asking for a new option, very useful when dispatching documents:
the ability to “force resync” on client site when he subscribe to a readonly directory/library.
It will avoid the problem if, by a false command, you delete files on the client.
On seafile client, you can manually “resync” a library, but it can by useful to have (on server side) a option like
“always sync if files are deleted on client”.

Thank you for your fantastic work!

Regards,
js.

3 Likes

Vote for this option too. As workaround maybe automate ‘resync’ on client via cron job, but seafile cli commands missing resync option: https://github.com/haiwen/seafile/issues/1791

My vote is to add a feature that allows you to set up a library as a mirror library, whereby the library is always mirrored to the client. That would eliminate the need for a manual resync.

Trying to understand Resync for my Windows client. Would be great if a comprehensive document explaining the feature is made available.

Basically the library failed to sync and am tempted to restart syncing.

https://www.seafile.com/en/help/unsync_resync/ does not do a good job at describing what the resync does in terms of data already available. Will it take the server version over the client’s? What if there are differences in the files?

Thanks.

It functions the same way as if you were to unsync a library and then set up a new sync to it. Only real difference is, you don’t have to go through and reassign the folder it syncs to.

Syncing means putting the most recent version out there. When you sync, it compares the two files. If there is a difference, then the most recent version is synced to the side that has the older version So, priority has to do with time rather than location.

Example… Let’s say you unsync a library. Then you copy a file to the client. Then, you set up the sync all over again. The file on the client will get synced to the server.

If the file has changed on both sides, then you have a conflict. In that case, Seafile creates a separate file with your login ID as part of the file name, and also the word “conflict” in it.