No not just once always sync from the Client to seafile but never sync from seafile back to the client. It would be a read only copy that is available in a seafile library that can be shared.
The files live on a NAS (Network Attached Storage). Using Seafile I would like to make these files available with a one way sync. If the files change on the NAS I want the client to propagate that to seafile but I don't want any changes made on the seafile side propagated back to the NAS. So if one is viewing files on seafile via a browser and decides to delete files that delete does not sync back to NAS. Actually the files would end up syncing back to seafile (oneway) in a self healing scenario
I know Seafile was designed to be two way with multiple clients but in this scenario I was hoping to have only one MASTER client and just push updates one way from the client to Seafile. I seem to recall an option to not allow updates (or define who can send updates) but I may be confusing it with other software.
Thanks for any input !!
P.S. As I type I realize if "I know the account password" then how would seafile know who the master client is. Still allowing an option on the client to Send Only / Receive Only / and Send And Receive to Seafile server may be a neat feature. As long as I am disciplined I could actually make the read only copy in seafile work.