Automated deployment of MediaWiki

From Freephile Wiki
Jump to navigation Jump to search

As a contributor to Meza, and developer of QualityBox, we've been closely following the efforts in the MediaWiki community around easier/automated deployments of MediaWiki. Actually, it's a goal of the MWStakeholders Group. And, it's a crucial aspect of the whole 2017 Wikimedia Technology Department Goals since at least 2018. Here is a list of some of the efforts and projects within and outside the WMF for automating deployments of MediaWiki:

WMF[edit | edit source]

Dev Images[edit | edit source]

WMF uses "Dev Images" in Release Engineering for their CI/CD pipelines There used to be a Gerrit repo for "dev-images", but it has now moved to GitLab The repo is about Docker images for local MediaWiki development. Can be used with Docker Compose and Kubernetes. Published to the WikiMedia Docker Registry, e.g.

There was a 2019 issue / pull request to create a MySQL/MariaDB image instead of Bitnami image(s) for MySQL/MariaDB

For Distributors[edit | edit source]

MediaWiki with Kubernetes[edit | edit source]

MediaWiki on Docker[edit | edit source]

Docker Library Docs specifies how Docker official images are made (ie. all the official images on Docker Hub). There is specific information for MediaWiki at These images are what users get when using MediaWiki Docker (see section below for further details).

Compared to a "developer" process, you can see what is going into WMF production images at the Wikimedia base docker images for production repository by lavagetto (Giuseppe Lavagetto)

MediaWiki Docker[edit | edit source]

MediaWiki-Docker is distributed with MediaWiki core. Just follow the directions in to create your Docker-based development environment. The images, and more information can be found on the MediaWiki page in DockerHub. The actual upstream repository (where images are built) comes from a WMF repo mirror on GitHub Wikimedia Git repo of the Docker official image for MediaWiki [1] Note that there are at least 3 variants you can choose from: Apache, FPM and FPM-Alpine.

There is a compose file which can be overridden to specify variants, "recipes" and options. While the Docker Hub image just derives from PHP, the Compose file specifically derives from the Debian Linux PHP image[2].

MediaWiki Docker Dev[edit | edit source]

MediaWiki-Docker-Dev (Addshore's GitHub repo) for using Docker and MediaWiki (Developers) See also: MediaWiki API library It's a library for making it easier to work with the MediaWiki API. Good to know/use/contribute. One member of a group of libraries to interact with WikiData, etc. (docs) Addwiki repos are by Addshore, Jeroen DeDauw and Sam Wilson.

Node Services[edit | edit source]

  • MediaWiki Node Services Run several MediaWiki nodejs services (RESTBase, Parsoid) in a single docker container. Useful for small / low-memory installs. By WMF's d00rman (Marko Obrovac - Croatia) and gwicke (Gabriel Wicke - Menlo Park)

Lex Sulzer[edit | edit source]

Configuration Management and Deployment at WMF[edit | edit source]

It should be noted that the WMF uses Puppet for configuration management (See the operations/mediawiki-config repo), and Scap3 (which is used in SWAT) (obsolete) for deployments. There is the Cloud VPS which is powered by wp:OpenStack for projects related to the Wikimedia movement. The environment includes access to a variety of data services. Cloud VPS is meant to make it easier for developers and system administrators to try out improvements to Wikimedia infrastructure (including MediaWiki), power research and analytics, and host projects that are not viable in the Toolforge environment. Virtual machines running on Cloud VPS are subject to the instance lifecycle.

Puppet[edit | edit source]

Config Settings[edit | edit source]

With any automation tooling and deployment, you will inevitably need to refer to the long list of MediaWiki Configuration settings.

  1. The repo was originally started as (forked from) Ben Hutchins' repo - which is now deprecated
  2. e.g. buster-php81-fpm:1.0.1-s2 which derives from Debian:10-slim