/home/user/folderX
/home/user/folderX
in general (~98%) the laptop only should receive the state of the desktop. In some situations some changes (like of some files or a folder) done on the laptop should be “synced” back to the desktop.
Given the scenario above, setting the desktop to “Send Only” and the laptop to “Receive Only” really isn’t a good fit.
One strategy would be to use two Syncthing folders…
Desktop:
/home/user/A
/home/user/B
Laptop:
/home/user/A
/home/user/B
Folder A would be “Send Only” on the desktop and “Receive Only” on the laptop.
Folder B would be “Send & Receive” on both devices.
Anytime the laptop needs to sync something to the desktop, drop it into folder B. On the desktop, move files/folders from B to A whenever they should no longer be modified by the laptop.
Another strategy would be to keep the single /home/user/folderX …
But set both sides to “Send & Receive”, and then use filesystem permissions to control what can and cannot be deleted by the laptop.
The downside is that there will be unresolved sync errors if the laptop tries to delete/change a file/folder that it doesn’t have permission to, but then that should only happen no more than ~2% of the time. 
No, because it’d defeat the intended purpose of a device setting a folder to “Send Only” if the recipient can arbitrarily override the sender.
I can’t think of a file transfer or sharing tool that can do what you’re asking out-of-the-box.
Currently I use a script on the laptop like
(when the desktop is online)
folderID="test"
syncthing cli config folders "${folderID}" type set sendreceive
sleep 30s
syncthing cli config folders "${folderID}" type set receiveonly
which is not nice but does what I “need” in some sense
Or you can use ‘send/receive’ on both devices, with rules or combinations on ‘ignore patterns’ on both devices. If the type and name of files that it handles allows it
Thanks for you idea
‘send/receive’ on the desktop is something that doesn’t feel so good (I would like to have it send-only → security/control about the “state-changes”)
my current opinion is, that there is “too much risk” if the ignore pattern is forgotten on a new device (setup) or the logic of folders and naming changes (Could we have a .stsharedignore file that gets synchronized between all the devices? · Issue #7311 · syncthing/syncthing · GitHub)
regarding the ignore pattern
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.