#User gid linux full

Next, make a default ACL to do the same, so that when a user creates subdirectories they still have this ACL: setfacl -dm g:33:rwxĪnd make sure there is a default ACL for the users group: setfacl -dm g:max:rwx If a user doesnt want a file or folder accessible to nextcloud, they can revoke this ACL.

#User gid linux full

This gives nextcloud full control over the home directory without letting any other user have such control (this is why you need ACLs, using a group is not fine grained enough). Next, use ACL to give permissions to the www-data user, which in my setup was userid 33: setfacl -m g:33:rwx This ensures that when a file or folder is created by nextcloud, the group owner will be the users personal group ID. Then make sure the setgid bit is set on the user home directories: chmod g+s /home/max Users home directories are configured with default permissions 770 and owner as username:usergroup (e.g.

Next, I set up ACL permissions on the remote drive (more on why later).

Not sure why Karl thinks it works different. I still think it would be nice to have proper uid/gid support.įirst of all, the linked PR works exactly how I thought it would, you set the mount point to ‘/’ (you can even do this on the GUI by entering / for the name) and the users root folder becomes the external storage. I managed to hack together a solution to this which I think is “good enough” and I’m going to leave it here in case other people are interested in this kind of setup.