-
-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Symlinks don't generate vhost files for Apache container #753
Comments
|
Currently not at my workstation to check the first two, but I was able to cd into the symlinks from inside of Devilbox, editing files also reflected back to my host machine just fine as well. I'll let you know first thing the output from those ls commands when I'm back at my workstation. |
Can you also try this |
Here's the output of those commands Local Machine: ❯ ls -lap api.company
lrwxr-xr-x 1 user staff 54 19 Nov 16:18 api.company -> /Users/user/Documents/Development/Company/api Docker Container: devilbox@php-7.3.24 in /shared/httpd $ ls -lap api.company
lrwxr-xr-x 1 devilbox devilbox 54 Nov 19 05:18 api.company -> /Users/user/Documents/Development/Company/api/ Local Machine www directory: ❯ ls -lap
total 16
drwxr-xr-x@ 6 user staff 192 19 Nov 16:34 ./
drwxr-xr-x 5 user staff 160 15 Oct 16:30 ../
-rw-r--r--@ 1 user staff 6148 15 Oct 16:30 .DS_Store
-rw-r--r-- 1 user staff 0 15 Oct 16:13 .keepme
lrwxr-xr-x 1 user staff 54 19 Nov 16:18 api.company -> /Users/user/Documents/Development/Company/api
lrwxr-xr-x 1 user staff 59 19 Nov 16:34 manage.company -> /Users/user/Documents/Development/Company/frontend I've also updated my check-config.sh output in issue description, I had a few permissions errors with my startup scripts, but those don't appear to have changed anything after fixing them. To also comment on why I believe this is an issue with watcherd, at this line: https://github.com/devilbox/watcherd/blob/master/watcherd#L102
I've also updated my httpd container's |
Thanks for figuring this out. PR is on the way. I've done it a bit differently by omitting any find GNU features to preserve compatibility with MacOS: https://github.com/devilbox/watcherd/blob/master/watcherd#L103 |
Thanks for the quick fix on this, appreciate it! |
Fix released here: #757 |
ISSUE TYPE
Checklist
.env
file is attached./check-config.sh
output is added belowdocker-compose logs
output is added belowdocker-compose.override.yml
is attached (if exists)cfg/
dir are attached (if exist)OS / ENVIRONMENT
SUMMARY
I've currently got two symlinks in my data/www folder that link back to folders with my projects in them.
These symlinks are fully accessible and all files within can be accessed within the php and httpd containers just fine.
This was accomplished via mounting the symlink targets via the docker-compose.override.yml file.
My assumption here is that symlinks aren't picked up by watcherd to trigger vhost generation.
STEPS TO REPRODUCE
Create a symlink to a directory from within your data/www folder to another folder
Add or update the following in your docker-compose.override.yml:
This should allow you to access the created symlink just fine inside of both containers.
When viewing the virtual hosts page in the devilbox intranet you'll be greeted errors on the symlink directories saying "No Host DNS record found. Add the following to /etc/hosts:
127.0.0.1 directory.loc"
And clicking on the config cog icon it will take you to a vhost config file that does not eixst.
EXPECTED BEHAVIOUR
Symlinks that have a folder set as their source should trigger watcherd to generate vhosts
ACTUAL BEHAVIOUR
Symlinks appear to be ignored by watcherd and no vhost file is generated
OTHER INFORMATION
Start command
Outputs
docker-compose logs
The text was updated successfully, but these errors were encountered: