By default the below steps will install MediaWiki at ~/dev/mediawiki
and start a server for http://default.web.mw.localhost:8080.
Many aspect of the container, including the port and MediaWiki path, can be customised
by creating a local.env
in this directory, in which to override one or more variables
from default.env
.
There is a setup script that you can run with INSTALL_DIR=~/src ./setup.sh
if you already have Docker
installed and want to skip the manual steps. Note that INSTALL_DIR
is the parent directory where MediaWiki
core will be downloaded, so in the example above you would end up with a codebase at ~/src/mediawiki
.
https://docs.docker.com/compose/install/
- Use the
docker-ce
package, not thedocker
package (read their install instructions) - If you want to avoid logging in as root or sudo commands, you will have to add your user to the docker group:
https://askubuntu.com/questions/477551/how-can-i-use-docker-without-sudo#477554
- This does not mean your containers will not run as root. These are different settings not really used currently by this dev setup.
git clone https://github.com/addshore/mediawiki-docker-dev.git
You can start without the skin but you will find that your MediaWiki install doesn't look very nice.
From Wikimedia Gerrit:
git clone https://gerrit.wikimedia.org/r/mediawiki/core /srv/dev/git/gerrit/mediawiki
git clone https://gerrit.wikimedia.org/r/mediawiki/skins/Vector /srv/dev/git/gerrit/mediawiki/skins/Vector
(You can clone your code to somewhere other than /srv/dev/git/gerrit/mediawiki
. For example, ~/src/mediawiki
but you'll need to follow step 6 carefully.)
Either on your host machine or with Docker, inside the /srv/dev/git/gerrit/mediawiki
directory:
docker run -it --rm --user $(id -u):$(id -g) -v ~/.composer:/tmp -v $(pwd):/app docker.io/composer install
A .docker/LocalSettings.php
file exists within the containers running Mediawiki. Your LocalSettings.php
file must load it.
Make a LocalSettings.php
in the root of the MediaWiki repo containing the following:
<?php
require_once __DIR__ . '/.docker/LocalSettings.php';
When you come to change any MediaWiki settings this is the file you will want to be altering.
For example after install you will probably find you want to load the default skin:
wfLoadSkin( 'Vector' );
Note: If you cloned mediawiki into a directory other than /srv/dev/git/gerrit/mediawiki
you will need to do this step, otherwise the defaults can likely be used.
Copy the content of default.env
from the mediawiki-docker-dev
dir into a new file called local.env
.
Alter any settings that you want to change, for example the install location of MediaWiki, a directory to a local composer cache, or webserver or php version.
Create and start the Docker containers:
./create
Update your hosts file:
Add the following to your /etc/hosts
file:
127.0.0.1 default.web.mw.localhost # mediawiki-docker-dev
127.0.0.1 proxy.mw.localhost # mediawiki-docker-dev
127.0.0.1 phpmyadmin.mw.localhost # mediawiki-docker-dev
127.0.0.1 graphite.mw.localhost # mediawiki-docker-dev
You can also use the ./hosts-sync
script to try and update it automatically if possible. You may
need to use sudo ./hosts-sync
instead if the file is not writable by the shell user.
The below commands are shell scripts in the mediawiki-docker-dev directory.
For example, the Up command can be invoked as ./create
, and the Bash command as ./bash
, etc.
To easily invoke these while working in another directory (e.g. mediawiki/core, or an extension) you can add a small bash alias to your bashrc
file. For example:
alias mw-docker-dev='_(){ (cd /$GITPATH/github/addshore/mediawiki-docker-dev; ./$@) ;}; _'
The below documentation assumes this alias in examples, but each of these also works directly. Instead of mw-docker-dev start
you would run ./start
from your Terminal tab for mw-docker-dev.
Create and start containers.
This includes installing a default wiki at http://default.web.mw.localhost:8080 with an "Admin" user that has password "dockerpass".
The spec of the system that this command will create is based on environment variables. The default spec resides in default.env
. You can customize these variable from a file called local.env
, which you may create in this directory.
mw-docker-dev create
Shut down the containers. Databases and other volumes persist. See also: Resume, Destroy.
mw-docker-dev suspend
Start (or restart) the containers. See also: Suspend.
mw-docker-dev resume
Shut down the containers, and destroy them. Also deletes databases and volumes.
mw-docker-dev destroy
Run commands on the webserver.
If the containers are running you can use ./bash
to open an interactive shell on the webserver.
This can be used to run PHPUnit tests, maintenance scripts, etc.
mw-docker-dev bash
You can add a new site by subdomain name using the ./addsite command
mw-docker-dev addsite enwiki
Check whether the hosts file contains all needed entries, and if not, shows which entries need to be added, and also tries to add them automatically if possible.
mw-docker-dev hosts-sync
Run git pull
in your the relevant Git repositories for MediaWiki core
and extensions.
If you need to apply schema changes after updating MediaWiki, or after installing additional extensions, you can follow the regular MediaWiki instructions. Just make sure you're on the web server when doing so.
For example:
$ mw-docker-dev bash
root@web:/var/www/mediawiki# php maintenance/update.php
Be sure to set default
(the wiki db), this is a multi-wiki environment.
For example:
mw-docker-dev phpunit-file default extensions/FileImporter/tests/phpunit
See also https://www.mediawiki.org/wiki/Manual:PHP_unit_testing
To run the QUnit tests from the browser, use Special:JavaScriptTest.
See also https://www.mediawiki.org/wiki/Manual:JavaScript_unit_testing.
To run QUnit from the command-line, make sure you have Node.js v4 or later installed on the host, and set the following environment variables:
export MW_SERVER='http://default.web.mw.localhost:8080'
export MW_SCRIPT_PATH='/mediawiki'
$ cd ~/dev/mediawiki
$ npm install
$ npm run qunit
While using PHP you can use remote xdebug debugging.
To do so you need to set IDELOCALHOST
in you local.env file to the IP of your local machine (where you run your IDE) as it appears to docker. Note with Docker for Mac, you can use IDELOCALHOST=host.docker.internal
.
xdebug connections will then be sent to this IP address on port 9000.
You can add additional services, or modify current services, by creating a docker-compose.override.yml
file (docs). For example, to add a Redis service, add these contents to docker-compose.override.yml
:
version: '2'
services:
redis:
image: redis
To modify a current service, for example to try a different volume caching for macOS like :delegated
instead of :cached
(file reference):
version: '2'
services:
web:
volumes:
- "${DOCKER_MW_PATH}:/var/www/mediawiki:delegated"
Note that the other volumes for the web
service will be merged, so you don't need to specify every volume mapping from the main docker-compose.yml
file in your docker-compose.override.yml
file.
- FIX HHVM strict mode
- Strict Warning: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function.
- Statsv endpoint
- Setup awesome hosts file additions & removals