I was actually looking for that when I was opening this issue but github has been changing for me lately. it seems reasonable to mark the deleted dir containing receive only items as receive only item too instead of gaining to sync/delete it. The local device is the one you are configuring, viewing status for, etc., while the remote device is. In keeping with Syncthing terminology they are going to be called devices in the rest of the documentation. Now when a file is deleted on the remote but restored on the clone, It will appear as a "Local Changes" on the clone, but when a folder is deleted on the remote that contains file and restored on the clone, syncthing throws an "Out of Sync" warning.Īlso, how did you manage to open an issue with no labels? I think the issue is that receive only items aren't synced, thus the remote can delete the directory containing the receive only files without touching them. For this guide let’s assume you have two machines between which you want to synchronise files. My setup is to clone a folder from the remote but retains the files deleted on the remote by restoring using the "Staggered File Versioning". Let say my android is the remote and has folder set to Send Only and my on my PC has a clone of that folder set Receive Only. ![]() The warning is in the title "Out of Sync" on the receive only folders. ![]() It's not clear what warning you are talking about, but the idea is that folders should look identical on both sides, if they don't they are out of sync.ĭeleting files on one side and expecting them not to be deleted on the other is not really syncing, it's more like file transfer which is not a scenario syncthing is made for.
0 Comments
Leave a Reply. |