First, add yourself into the group
chgrp www-data /home/myuser/folderA
chmod g+rwxs /home/myuser/folderA
Should do the trick unless the permissions on your
/home/myuser do not permit other users access.
The first command changes the group ownership of the folder to that of the webserver. The second command gives members of the
www-data group read, write, enter-directory rights, and the group
s flag will ensure that any files that get created inside that directory take
www-data as the group - so if you create a file as
www-data user will have access.
Nb. this also depends on the
umask settings of both your user account and the webserver: you need to make sure that files created in folderA have group
rw access (and directories created within need group
If your webserver does not have enter rights into your
/home/myuser dir (quite sensible) then it's not going to get in there unless you do something else. Two solns:
sudo mount --bind /home/myuser/folderA /var/www/mysite/folderA (this is an ugly hack and would have to be repeated after reboot. But a powerful trick, also can be used to make folders accessible inside SSH jails.)
Simply move the shared folder somewhere else, e.g.
The 2nd option is nicest. Let's say the stuff in folderA is really public and you don't care who sees it, you can set it up like
sudo mkdir -m777 /home/shared-stuff
Then you can put inside that, say, folderA with permissions as above, and folderB that www-data should not have access to with different permissions, e.g.
$ cd /home/shared-stuff ; ls -l
drwxrwsr-x 2 myuser www-data 4096 Jan 17 21:46 folderA
drwxrwx--- 2 myuser myuser 4096 Jan 17 21:46 folderB