Timeline for Drush fails after moving to another server
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 29 at 2:57 | review | Close votes | |||
| Oct 13 at 3:06 | |||||
| Aug 31 at 16:21 | answer | added | Ataron Chronon | timeline score: -1 | |
| Aug 26 at 13:21 | comment | added | Stef Van Looveren | This is a bug I encountered upgrading from Drupal 9. I had to downgrade to Drush 11.1.1 to get everything working again. | |
| Aug 20 at 15:40 | comment | added | sapinva | Composer gets to blame me this time. I had "composer" in my .gitignore, intending to ignore www/composer, not www/vendor/composer. Having vendor in your doc root should make no difference, but you do have to check all the files into git. | |
| Aug 19 at 22:12 | comment | added | sapinva | @Clive Maybe I'll run composer require drush/drush on the server and diff the changes. | |
| Aug 19 at 22:07 | review | Close votes | |||
| Sep 5 at 3:06 | |||||
| Aug 19 at 21:42 | comment | added | leymannx | Sometimes it happened I've accidentally run composer install in the webroot and then had two vendor folders, one in the webroot and the real one above. This messed things up (and took a long time to find out 🤦). | |
| Aug 19 at 20:59 | comment | added | Clive♦ |
It's not likely Composer is making assumptions, or doing anything wrong per se; barring bugs it will only do what it's told, and this doesn't sound like a bug. A typical modern Drupal installation has a composer.json above the web root, which is configured to install packages to vendor/, <webroot>/core, <webroot>/modules/contrib, and so on - seeing a <webroot>/vendor/ folder implies you're not following the usual practice, so it's difficult to advise
|
|
| Aug 19 at 20:55 | comment | added | sapinva | So you think composer is making autoload files that assume site/vendor and site/www? It was originally a d8 site, but has been updated many times since without this issue. | |
| Aug 19 at 20:49 | comment | added | Clive♦ |
/var/www/html/xxx/www/vendor/drush is an unusual path, you would normally expect to find drush in /var/www/html/xxx/vendor. Maybe you have a custom solution which needs upgrading along with the Drupal version
|
|
| Aug 19 at 20:47 | comment | added | sapinva | Yes, it is there. All the files are there, repo includes everything but settings.php. And running git status shows no old files leftover on the server, everything is in the repo. | |
| Aug 19 at 20:44 | comment | added | mona lisa |
You are blaming Composer yet you did not run it on the server. Did you in fact look to see if the class file for Drush\DrupalFinder\DrushDrupalFinder is among the files you deployed?
|
|
| Aug 19 at 20:42 | comment | added | sapinva | I did not. It has to pull from the git repo and run as is on all servers. | |
| Aug 19 at 20:37 | comment | added | mona lisa |
Did you composer install after moving to this platform?
|
|
| S Aug 19 at 20:29 | review | First questions | |||
| Aug 23 at 4:10 | |||||
| S Aug 19 at 20:29 | history | asked | sapinva | CC BY-SA 4.0 |