Composer
Composer je správce závislostí pro knihovny PHP. Starting with MediaWiki 1.25, MediaWiki core's external library dependencies are being managed with Composer. In addition, it can be used to manage the installation of MediaWiki extensions (available since MediaWiki 1.22). However this is currently not well supported. This may change in the future.
Installing Composer
 | MediaWiki supports Composer 2.x as of MediaWiki 1.35.2 and later. |
On Unix/Linux and macOS
There are multiple ways to install Composer, besides the most obvious way, sudo apt install composer.
Only Composer 1.x is supported by MediaWiki 1.31, 1.35.0 and 1.35.1. To grab the latest Composer 1.x stable release:
wget -cO - https://getcomposer.org/composer-1.phar > composer.phar
Composer 2.x and Composer 1.x are supported by MediaWiki >= 1.35.2 (along with the REL1_36 branch and master). To grab the latest Composer 2.x stable release:
wget -cO - https://getcomposer.org/composer-2.phar > composer.phar
For users on macOS, you can use Homebrew to install Composer.
Note this will install version Composer 2.x, so depending on the version of MediaWiki you are using, you may need to follow the wget instructions above instead to download Composer 1.x. To install using brew:
brew install composer
If that doesn't work, or you do not have Homebrew installed, you can try:
php -r "readfile('https://getcomposer.org/installer');" | php
Toolforge and the extension distributor use the copy of Composer contained in the "integration/composer" git repo.
Once Composer is installed, you can run commands via the downloaded phar:
php composer.phar someCommand
You may want to move the phar into your path so it can be used as a normal executable:
mv composer.phar /usr/local/bin/composer
composer someCommand
If the mv command fails due to permissions, execute it again with sudo.
sudo mv composer.phar /usr/local/bin/composer
composer someCommand
On Windows
Just download and run the installer from the download page. If you prefer manual installation, you can follow the above steps except that Windows doesn’t have wget (or APT or Homebrew) by default, and there is no /usr/local/bin directory. In these cases, you can just download composer-1.phar in your web browser and then rename it to composer.phar.
Local installation
You're not out of luck if you don't have permissions to run Composer on the server. It is also possible to download the MediaWiki folder to your local machine, install and run Composer, and transfer the files back to the server.
Upgrading Composer
Composer 1.x
If you want to upgrade Composer to the latest 1.x stable (or downgrade from 2.x stable), you can use:
composer self-update --1
If the update command fails due to permissions, execute it again with sudo.
sudo composer self-update --1
If you are on a really old version of composer, it may not have the --1 parameter. In this case, you might want to run self-update twice. The first may update it to 2.x, so the second will downgrade it to the latest version of 1.x.
composer self-update
composer self-update --1
Composer 2.x
If you are using Composer 1.x, and want to upgrade to Composer 2.x (and are using an appropriate version of MediaWiki, such as >= 1.35.2), you can use:
composer self-update --2
If the update command fails due to permissions, execute it again with sudo.
sudo composer self-update --2
Usage in MediaWiki core
MediaWiki 1.25+ depends on some external libraries which are managed with Composer.
Composer creates an autoloader at vendor/autoload.php, which is included by WebStart.php.
Composer managed dependencies are bundled into tarball distributions of MediaWiki and extensions so system administrators do not need to use Composer directly.
When installing MediaWiki using Git, dependencies declared in $IP/composer.json can either be installed locally by running composer update --no-dev or the mediawiki/vendor.git repository can be cloned to provide the same libraries used on the Wikimedia production cluster.
Using composer-merge-plugin
MediaWiki core "owns" $IP/composer.json and will change the contents of that file in both tarball and Git managed updates.
In order to allow local installs to use Composer to load optional libraries and/or manage extensions with Composer, a special plugin for Composer named composer-merge-plugin was developed.[1]
This plugin and the MediaWiki core composer.json configuration allow a local deployment to add required extensions and libraries to a file composer.local.json inside the root MediaWiki directory.
composer.local.json can also be used to install Composer managed libraries that are needed by extensions that are not installed using Composer themselves.
This is only needed when the extensions are not installed from tarballs generated by Extension Distributor.
To enable Composer to discover and process the composer.json files that may be included in any and all of your locally installed extensions, add something like this to $IP/composer.local.json:
{
"extra": {
"merge-plugin": {
"include": [
"extensions/*/composer.json",
"skins/*/composer.json"
]
}
}
}
After any changes to composer.local.json, you need to run composer update so that Composer will recalculate the dependencies and the changes will take effect.
Resources
- How to install extensions through Composer
- How to add external libraries to MediaWiki core or extensions
- Best practices when creating a composer.json
- Information about adding packages to packagist.org
- w:Composer (software)