Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.With composer an essential part of Drupal 8 many projects may now begin to specify composer dependencies. Site builders are often using shared hosting environments without command line access and/or without the ability to install composer.
As such - Drupal and Drupal.org needs to provide a way for site builders to use projects that specify composer dependencies.
This will likely require two components:
1. Something like project_browser on the user's Drupal website, that can communicate with Drupal.org to specify the modules/versions being used on the site. This should also be connected to the updates process.
2. On Drupal.org's back-end something to compile the modules/versions from a site and generate tar.gz packages with the appropriate dependencies for the site builder to upload.
Comments
Comment #2
hestenetIt may be possible to simplify this:
"A system within Drupal, like the updates system, that traverses the file system looking for composer files sending the meta data to Drupal.org and then send back a /vendor directory that can be packaged up and uploaded." per @mixologic
Comment #3
hestenetComment #4
hestenetPostponing until the initial composer facade is in place.
Comment #5
hestenetComment #6
hestenetComment #7
hestenetComment #8
hestenetComment #9
gagarine commentedI'm not sure about this issue 5 years later. Anyone is going to invest time in this? The way forward isn't simply to use composer to install dependencies? Their is now a lot of cheap hosting with SSH.
Alternatively peoples can use https://php-download.com/ or other GUI build on top of composer.
Comment #10
cilefen commentedI think #2940733: Site Builder Tool/Project Browser initiative is where this is occurring now. Should we close this?
Comment #11
drummYes, I think so.