Thank you for replying so fast.
Do you remember if there is any public info about what you agreed on? May it be this?
[quote=“calmh, post:9, issue:215”]As I see the “pause sync” feature (that this issue is for), it would;
-
Be per repo, i.e. not global (although you could pause all repos one by one)
-
Prevent scanning, i.e. when paused we do not scan for local changes
-
Prevent pulling, i.e. when paused we do not try to get outdated files in sync
-
Not affect connections, i.e. we still connect and attempt to stay connected to other nodes (this includes sending periodic ping messages).
-
Not affect incoming data, i.e. we don’t try to stop other nodes from sending us index updates[/quote]
Anyway, in your responses to this thread I’ve realized that you are already working on a solution which may solve this use case:
[quote=“Tracerneo, pull/2417”]Particular master/slave setting combinations should work as described:
-
both false – normal push&pull folder, keep in sync
-
master true – push-only folder, not accepting changesets
-
slave true – pull-only folder, copy pushing nodes, always override local changes
-
both true – no push nor pull, locally inform about sync status, possibly allow downloading as a mirror[/quote]
When that feature is merged to the main branch, either slave true or both true will suffice.
Meanwhile, is it secure to point syncthing to a symbolic link and remove it to emulate the “pause sync” state?