Consider this as a FAQ: Why does installation without drush require a bunch of manual steps?

The module page states:
"By using this [drush pm-enable] technique, Composer will be downloaded and the appropriate commands will be run automatically without having to do anything outside of normal Drush workflows."

If Drush can do this on install, than why can't Drupal? Is it purely a matter of getting responses to a bunch of yes-no questions from the user? Can't we just assume that the user is going to answer YES because enabling the module is the end goal?

Comments

cpliakas’s picture

That's a great question.

The challenges that come to mind are that the web server might not (and probably should bot) have access to write to the vendor directory. Composer is also a command line tool which would have to be executed through the web UI, so there could be challenges around that. Composer is a pretty memory intensive process that takes a long time to execute, so there would be the danger of OOMing or timing out.

With Drush, it is already on the command line so the workflows are easier to integrate without the risks highlighted above.

Happy to explore this further, though. I am open to making this work better through the UI.

cpliakas’s picture

Issue summary: View changes
Status: Active » Closed (duplicate)

Closing this as a dup of #2203363: Provide an application or service to build dependencies when a composer.json file is received, since there will likely need to be another service or app to address the steps that you need to do if you are not using the command line.