Closed (duplicate)
Project:
Composer Manager
Version:
7.x-1.0-beta7
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
24 Oct 2013 at 02:30 UTC
Updated:
23 Feb 2014 at 16:57 UTC
Jump to comment: Most recent
Comments
Comment #1
cpliakas commentedThat'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.
Comment #2
cpliakas commentedClosing 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.