I tested (as you see in the beginning in my post) in April 2019 with the version they had at that time and read-only worked as expected.
That said I don’t think Nextcloud is better - in contrary: Seafile has a much better sync.
I only took Nextcloud as reference in order to give an example how it could be implemented from a user perspective.
1 Like
Does anybody know if there will be progress on read-only file sync?
The statement I gave before still holds in our opinion. So currently there is no plan for further changes.
Hi everyone,
As far as I can tell, the issue is still there. The situation is the following: We have several read-only folders, users have Seafile clients installed on their Windows PCs, and they like working with files using file managers (Explorer, Windows Commander, Far, etc.), so they won’t see any warning messages indicated by the client window. One of the users makes a mistake, for instance, renames or edits a file in a read-only folder. Then the owner of the file updates it on the server. We expect the problematic file to be updated in the locel folder, due to automatic sync. Alas, the mistakenly edited file is still there, and I consider this to be a major issue.
The best way of preventing such issues would be if the system did not allow to save the file. If, for some reason, this is impossible to implement, then we would naturally expect replacing the file with a new one, when it is updated, otherwise, working with such folders becomes a pain.
The best way of preventing such issues would be if the system did not allow to save the file
I think you’re right.
I haven’t tried it yet, but possibly the solution is for computer admins to make the local directories read-only to the users (but allow seafile client to write) via the OS.
eg:
- In windows/linux set the read-only directories to read-only for the user (so it’s impossible for them to make changes)
- run seafile client as a different user / different permission level so that it can still sync new library changes to the local directory.