Yeah, he polls the api waiting for a 10 minute period when the list of files needed is zero.
Today I was thinking that the event api http://docs.syncthing.net/dev/events.html might be the way to go. My scenario is a bit different since syncthing would be launched when I start the “one run”, so I probably need to wait for it to connect to some devices, watch the transfer progress, etc. But not too different.
I can’t tell if a “get into sync and then exit (or timeout)” feature would be a good feature addition or not.
That answers my question then. The idea makes some sense, it’s sort of possible with the API, and yeah it might make an useful feature.
My initial reaction was: “Ought that not be –sync-once-with |all.” But that lead to …
Yeah, it’s a bit tangled if you have N partner devices and the folders are scattered over those partners. Might argue that the configuration is what it is. So one time means sync all the folders with all the partner devices or timeout. I.e. –sync-once-with-timeout <seconds>
Might be a role for args that narrow the configuration to a particular device of folder even for 24/7 syncing.
I’d very much appreciate such an option. One important use case for me is to keep some folders on my phone and my laptop in sync. Such an option would be ideal for that since I want to turn of WLAN on my phone once syncthing is done.