[POC] Using Bind Mounts for Non-root access

[dhsathiya]

Context

For non-root access to site files, we have to move from Volume mounts to Bind mounts. It also gives the flexibility to move site files to another location as well as initiate site in a git dir :tada:

Working

1. Create a site directory to some other path.

mkdir -p /home/vagrant/site/example.com

2. Copy the contents of app to the new directory

cp /opt/easyengine/sites/example.com/app/* /home/vagrant/site/example.com/

3. Change permissions of the newly copied files

chown -R home/vagrant/site/example.com/

4. Update site docker-compose.yml Replace "htdocs:/var/www" with "/home/vagrant/site/example.com:/var/www" under

services > { php , nginx } > volumes

5. Disable and enable site.

ToDo

• [x] Need to check host user groups and other related filesystem permissions to make the edits working with www-data user of the container. on host: adduser vagrant www-data maybe this also sudo chmod -R g+w /srv/www

[danish17]

@dhsathiya, Re-enabling/refreshing the site reverts the changes made to site's docker-compose.yml back to htdocs:/var/www.

[dhsathiya]

@danish17 that is expected behavior as those commands will recreate the docker-compose file. This POC has to be implemented in the code.

[dipankardas011]

yes

docker host mount

host file system