search

acquia / acquia-ra-composer

Example composer.json and repo architecture that works with Remote Administrations Acquia Automation. **Maintained by Remote Administration.**
9 stars 17 forks source link

Unable to run composer installed Drush on DevDesktop #27

Open l-laziz opened 3 years ago

l-laziz commented 3 years ago

When application specific Drush is installed as part of RA composer template, it causes conflict with system wide installed Acquia DevDekstop Drush. As result, it renders Drush completely unusable by throwing error: "The filename, directory name, or volume label syntax is incorrect".

The only way to run it as of now is by invoking Drush commands directly from "vendor/bin" dir instead of usual webroot.

https://github.com/acquia/acquia-ra-composer/blob/7e4665826dcb6c641d385f52cbd9505f3aa155cb/composer.json#L23

mohammadzo commented 3 years ago

@l-laziz I am going to update the composer.json. Drush 8 is on the platform. We recommend to install Drush 9 via composer. Please file a support ticket and I will be happy to troubleshoot your issue.

l-laziz commented 3 years ago

I tried Drush 9 as well and got the same exact outcome. Error: "The filename, directory name, or volume label syntax is incorrect".

Running "drush -d -d status" gives this:

Loading drushrc "C:\Program Files (x86)\DevDesktop\tools\vendor\drush\drush\drushrc.php"[bootstrap] into "drush" scope. [9.53 sec, 3.01 MB] Cache HIT cid: 8.1.17-commandfiles-0-6a2c749a197789450570847bc9a57ed2 [9.93 sec, 3.05 [debug] MB] Begin redispatch via drush_invoke_process(). [11.18 sec, 8.17 MB] [notice] Backend invoke: [command] "C:\Users\username\Sites\devdesktop\webroot\vendor\bin\drush" --root="C:\Users\username\Sites\devdesktop\webroot\docroot" --debug --verbose core-status 2>&1 [11.37 sec, 8.18 MB] Calling proc_open("C:\Users\username\Sites\devdesktop\webroot\vendor\bin\drush" --root="C:\Users\username\Sites\devdesktop\webroot\docroot" --debug --verbose core-status 2>&1); The filename, directory name, or volume label syntax is incorrect. End redispatch via drush_invoke_process(). [11.48 sec, 8.18 MB] [notice]

mohammadzo commented 3 years ago

@l-laziz Could you please file a Support tickets.