Closed sprankhub closed 4 years ago
Interestingly enough, having the config file var/cache-clean-config.json
in place does fix this specific error. However, maybe this can be handled more gracefully then?
Okay not really - I could not reproduce the issue at the same place after generating the config file, but changing something in another file brought up the same error again.
I don't think this is possible with the out-of-the-box env.php
, because the in-docker container DNS names don't resolve on the host machine, even if the ports of the services are exposed.
It would be cool to be able to run the watcher on the host machine, but I don't think that is possible by making changes to the cache-clean.js
tool. If the warden team somehow is able to create resolvable routes to the services from the host machine, and use those in the env.php
file, then running the watcher locally should "just work".
For now, I think I'll have to close this as a wont-fix
- sorry :'-(
Maybe you have time to create a PR to warden, or maybe open an issue at https://github.com/davidalger/warden/ for this?
For future readers, it might be possible to run warden env exec php-fpm vendor/bin/cache-clean.js -w
from the host machine instead of vendor/bin/cache-clean.js -w
I currently try Warden and would love to use the cache clean tool with it. I would love to run it from my host machine and not the Docker container. This has the advantage that I can simply open the PhpStorm project and PhpStorm will run the file watcher automatically. I read https://github.com/mage2tv/magento-cache-clean/blob/master/doc/docker-and-vm.md to get started. And I think it might be a good idea to run the
generate-cache-clean-config.php
script and check if this helps. However, I do not think that the following error would really be fixed with it. Here is the full output:Do you understand what is happening here, @Vinai? Is this something, which could be handled?