Problem
MediaWiki's composer.json does not define a type which means it uses the default type of library.
This means the installation directory (the web root) cannot be customized by installers like Composer Installers.
Solution
Set the type to mediawiki-core which is similar to what other projects do.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Set the package type to 'mediawiki-core' | mediawiki/core | master | +1 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T178137 MediaWiki-Vendor creates a scenario in which incompatible versions of dependencies can be present | |||
| Open | None | T166956 Cannot use Composer's CLI to manage a project's dependencies | |||
| Resolved | dbarratt | T190386 MediaWiki is not a library, so it should define a custom type in composer.json |
Change 421212 had a related patch set uploaded (by Dbarratt; owner: Dbarratt):
[mediawiki/core@master] Set the package type to 'mediawiki-core'
Sounds sensible.
A custom type doesn't mean that you have to have an installer to match that type does it? Just that it is possible to?
Just out of interest, a few other well-stared Github PHP projects that do specify a type mostly seem to use project:
https://github.com/LavaLite/cms/blob/master/composer.json "type": "cms",
https://github.com/getgrav/grav/blob/develop/composer.json "type": "project",
https://github.com/pagekit/pagekit/blob/develop/composer.json "type": "project",
https://github.com/anchorcms/anchor-cms/blob/master/composer.json "type": "CMS",
https://github.com/PrestaShop/PrestaShop/blob/develop/composer.json "type": "project",
https://github.com/pyrocms/pyrocms/blob/3.4/composer.json "type": "project",
https://github.com/drupal/drupal/blob/8.6.x/composer.json "type": "project",
https://github.com/bcit-ci/CodeIgniter/blob/develop/composer.json "type": "project",
https://github.com/jcc/blog/blob/master/composer.json "type": "project",
Correct.
It's similar to what Drupal does:
https://github.com/drupal/drupal/blob/8.6.x/core/composer.json#L4
Though as you pointed out, Drupal does wrap the "core" cms with a wrapper (within the same repo), our "project" wrapper would be in a different repo, see: T166956: Cannot use Composer's CLI to manage a project's dependencies
It can be.. but that's not one that Composer Installers currently supports:
http://composer.github.io/installers/
they do support drupal-core ... we could ask though which they would prefer... maybe Drupal should be the one to change. :P
Looks like mediawiki-core is the winner.
https://github.com/composer/installers/issues/390#issuecomment-378830925
Adding mediawiki-core to Composer Installers
https://github.com/composer/installers/pull/391
mediawiki-core is now supported by Composer Installers
https://github.com/composer/installers/pull/391
If you have composer/installers installed, executing composer require mediawiki/core will copy mediawiki into ./core (new functionality) instead of ./vendor/mediawiki/core (current functionality).
As far as our current workflow(s) goes, no, this shouldn't make any functional difference, it only makes a difference if your project requires mediawiki/core (which, afaik, nobody is doing). Right now, it would be broken anyways because it would be installed in the vendor directory.
I should note that if you do not have composer/installers installed (or any other installer plugin that can handle the mediawiki-core type), it will continue to work as it currently does, downloading mediawiki/core into ./vendor/mediawiki/core.
Right now, it would be broken anyways because it would be installed in the vendor directory.
Not necessarily cause for breakage. Wikimedia's production also uses a wrapper, called multiversion (MWMultiVersion). Which uses a slimmed down public root, in which only a few entry points like index.php exist, and certain static resources are exposed. This isn't unlike WordPress's approach to entry points.
In turn, these entry points include MediaWiki and run it. The current directory name used there is ../php-master (Beta Cluster) and e.g. ../php-1.31.0-wmf.29 (wmf production).
Can you point me to the repo for this? (I'm having trouble finding it). Though.. given that we have a MediaWiki-Vendor, I doubt they are loading core with Composer, but I can double check.
Change 421212 merged by jenkins-bot:
[mediawiki/core@master] Set the package type to 'mediawiki-core'