@mlusetti Can you please explain the initial problem you're trying to solve here? Obviously it's about filesystem permissions - can you show a clear example of what the ones that are problematic for you look like, and elaborate on the issue at hand? The fact that you want to use Syncthing isn't something that should be impossible to do out of the box per se.

@mlusetti Can you please explain the initial problem you're trying to solve here? Obviously it's about filesystem permissions - can you show a clear example of what the ones that are problematic for you look like, and elaborate on the issue at hand? The fact that you want to use Syncthing isn't something that should be impossible to do out of the box per se.

The main issue is I need or will to use different "unix" users to run rest-server and syncthing giving each one a "unix group" in common so I can give the group "read" permission on rest-server storage directory so I'm pretty sure the syncthing process will never write to rest-server storage directory but only read even if I misconfigure it.

@rawtaz Thanks for your attention.

That effectively means that it would be enough to have the option to store files and directories such that they are group accessible. Then you can use ACLs to grant syncthing access to your repository?

That effectively means that it would be enough to have the option to store files and directories such that they are group accessible. Then you can use ACLs to grant syncthing access to your repository?

Yes, using ACL or just standard unix permissions. Anyway that would be enough.