Description:
The library assumes that your WordPress installation is in a web/ folder in the same directory as the docker-compose, but doesn't mention this anywhere in the docs (and is different from Laravel which uses public/.
It would be useful to be able to customise this (without having to publish the config), and I think the docs should mention the requirement.
Solutions
I'm happy to have a go at both and submit a PR, but wanted to check if you had any opinions on how it should be done.
We could set an Environment variable something like WP_CLI_PATH which would be passed to any calls to wp (or we could use the wp server specific --docroot=
Or we could be more specific and specify the webroot path (though I'm not sure whether that'd ever be more useful than being able to set the root in general?).
Any thoughts?
Description:
The library assumes that your WordPress installation is in a
web/folder in the same directory as the docker-compose, but doesn't mention this anywhere in the docs (and is different from Laravel which usespublic/.It would be useful to be able to customise this (without having to publish the config), and I think the docs should mention the requirement.
Solutions
I'm happy to have a go at both and submit a PR, but wanted to check if you had any opinions on how it should be done.
We could set an Environment variable something like
WP_CLI_PATHwhich would be passed to any calls towp(or we could use thewp serverspecific --docroot=Or we could be more specific and specify the webroot path (though I'm not sure whether that'd ever be more useful than being able to set the root in general?).
Any thoughts?