This repository was archived by the owner on Apr 17, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 17, 2024. It is now read-only.
Drush is required to install composer #29
Description
Hi,
I've followed the instruction exactly but I get:
» docker-compose exec php composer run-script install:with-mysql
> scripts/install-mysql.sh
./scripts/install.sh: line 23: /var/www/vendor/drush/drush/drush
: No such file or directory
ERROR Drush is required to install Contenta CMS. Please install Contenta CMS using Composer. See http://www.contentacms.org/#install
Script scripts/install-mysql.sh handling the install:with-mysql event returned with error code 5
Drush is installed correctly in the vendor directory and the path to it in the script seem ok.
Someone has an idea ?
Activity
mrleblanc101 commentedon Feb 4, 2019
Seem like it used my local composer.
I had to composer global remove drush/drush
Is this a bug ? Shouldn't it use the composer in the docker container ?
e0ipso commentedon Feb 8, 2019
Maybe @pcambra knows the answer to the question above ☝️.
MykaMart commentedon Jul 25, 2019
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?
trevortwining commentedon Aug 7, 2019
Same issue here. Working on it today. If I resolve it, I'll submit a PR.
pcambra commentedon Sep 18, 2019
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?
MykaMart commentedon Nov 17, 2019
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.
pcambra commentedon Nov 18, 2019
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