i need some feature, that is called Read/Write Access and Read-Only on BTSync. I guess for my case it is the only missing thing besides Proxy-support.
if a node has got the RW-Key , it can send the repo to other nodes
if a node is only read-Only, it can only receive and distribute the files.
So there should be a possibility to have more contributors for one Repository, thats the goal.
Maybe a FolderMaster/FolderMaster-Sync would be a small solution for this.
also described here:
I want to sync my files between three servers. I want two servers to be masters (any changes on any of them will change files on all servers) and one server to be slave (masters just overwrite any changes there).
Is it possible?
thanks and sorry for raising this again… but this seems to be a pretty need
Maybe instead of master as a per repo setting we should do something like this as a checkbox for every node under “Share with Devices”, something like “do not accept changes from this node”.
I could imagine a solution to get something like this with the current implementation of the master:
-Devices with write access have a repo “abc” which they don’t share with the devices that should be read only
-devices with write access add another repo “abc-readonly” which points to the same folder as “abc” and set the option “Folder Master” and share it only with the devices that get read only.
see if you get errors thrown at you because this is probably a bad idea
(should work if you only have one master that distributes the repo to the readonly devices)
@Alex: yes, indeed. thats the readonly-flag (key) for users as implemented on BTSync…
so a checkbox per Device “do not accept changes from this node” would implement the same.
you are completely right. thanks for this suggestion
Continuing the discussion from
Three node syncthing with two masters:
But I think there is a relatively simple solution. Suppose you want changes to be synced two-way between A and B, but you want C to accept all changes and not propagate any (so A and B would both be masters, and C would be what other software calls read-only nodes).
Suppose the things you want synced live in directory ~/D1 (at least in machine A).
In A add two folders (I mean, “Folders” in the sense of the user interface of ST, not in the “directory of a filesystem” sense)
both of them use as Folder Path ~/D1, but in A-one-way-C, “Folder master” is checked.
Now, in both B and C accept the creation of the new folder, use ~/D1 (or whatever) in your filesystem, and you are done.
I just tried it, and it works fine. The key idea is that syncthing has no trouble using the same directory in different “Folders”, so you can share it in different ways (as “Master” and as non master).
This is not as simple as checking boxes for “read only”, etc, but it seems to work and is just fine (at least for small numbers of interconnected nodes).
P.S. You might also think about adding, in B, a
but this to me is confusing and when playing with it, it can lead to trouble. This makes sense: if you have just
it is unambiguous how changes can and cannot propagate. If you add B-one-way-C then it ain’t.