-
Notifications
You must be signed in to change notification settings - Fork 30
Drush is required to install composer #29
Comments
Seem like it used my local composer. |
Maybe @pcambra knows the answer to the question above ☝️. |
I'm running into this issue as well. An inspection inside the running container confirms that it missing the nested /vender/drush/drush folder in /var/www. Anyone have any thoughts on how to remedy this? |
Same issue here. Working on it today. If I resolve it, I'll submit a PR. |
I've updated both composer and moved to a more modern mode to install drush using cgr on 80a41a1, could you confirm this is fixed? |
It was not, Contenta was still unable to find drush where it was expecting it during the install. I have created a pull request that solves the issue. The new Dockerfile creates the folder structure the installer is expecting and creates a symlink between the new folder and drush. I have tested this fix and was able to complete the install. |
I must be missing something because according to the commit above and this contentacms/contenta_jsonapi@a8cd75b, there should not be a need for global drush, maybe we should explore why local drush is not being run |
Hi,
I've followed the instruction exactly but I get:
Drush is installed correctly in the vendor directory and the path to it in the script seem ok.
Someone has an idea ?
The text was updated successfully, but these errors were encountered: