Symbolic link not allowed or link target not accessible - can't make use of symbolic link for project

[cytopia]

Symbolic link not allowed or link target not accessible - can't make use of symbolic link for project

[jpuck]

@cytopia For me, I've got projects all over my file system that I'd like to be able to load in devilbox.

/var/www/project1
/srv/project2
/home/jeff/project3

I'd like to be able to symlink to these projects from HOST_PATH_TO_WWW_DOCROOTS

mkdir -p /devilbox/data/www && cd /devilbox/data/www
mkdir project1 project2 project3
ln -s /var/www/project1 project1/htdocs
ln -s /srv/project2 project2/htdocs
ln -s /home/jeff/project3 project3/htdocs

but this doesn't work because symlinks to real paths outside /devilbox/data/www are not followed.

[jpuck]

This would be a very convenient option to solve so that one could have the flexibility of storing projects anywhere on the filesystem instead of grouped in $HOST_PATH_TO_WWW_DOCROOTS

[cytopia]

@GiorgosK

You can set the main path of your www folders inside .env file:

HOST_PATH_TO_WWW_DOCROOTS=/home/giorgos/share/gwebsites/devilbox/data/www

Correct me if I understood something wrong.

[cytopia]

Are those symlinked directories actually present inside the docker after startup?

[jpuck]

I don't think so. I guess this could be a limitation of docker whereby volumes can't follow symlinks.

[cytopia]

@jpuck I am sorry to hear, then there is not much I can do about it.

[cytopia]

Might be related to: #90