Hi,
I’m using Phpactor inside a fully Dockerized Neovim setup. Works good, but I think I am not using the phpactor's cache and project settings properly.
This is how I run neovim with the phpactor in the same container it:
docker run --rm -it -w /app -v $PWD:/app localhost/minivim:stable
Each project is mounted into the container. Currently, I mount every project as:
/app
So different projects may have the same path inside Docker.
For example the host path is:
/customer-a/magento
/customer-b/magento
both become:
/app
My question is: does Phpactor use the full project path for cache or project identification?
Would it be better to mount projects inside the container using a more unique path, like:
/projects/customer-a/magento
/projects/customer-b/magento
instead of always using /app?
I want to avoid cache conflicts and make sure project-specific settings work correctly. I think I may also need to mount phpactor's configuration as a volume too so that it persists between the multiple coding sessions.
Thanks!
Hi,
I’m using Phpactor inside a fully Dockerized Neovim setup. Works good, but I think I am not using the phpactor's cache and project settings properly.
This is how I run neovim with the phpactor in the same container it:
docker run --rm -it -w /app -v $PWD:/app localhost/minivim:stableEach project is mounted into the container. Currently, I mount every project as:
/appSo different projects may have the same path inside Docker.
For example the host path is:
both become:
/appMy question is: does Phpactor use the full project path for cache or project identification?
Would it be better to mount projects inside the container using a more unique path, like:
instead of always using /app?
I want to avoid cache conflicts and make sure project-specific settings work correctly. I think I may also need to mount phpactor's configuration as a volume too so that it persists between the multiple coding sessions.
Thanks!