Wikibase/Docker/ig

Nchịkọta


Nke a bụ ntuziaka nzọụkwụ site na iji Docker wụnye Wikibase Suite na kọmputa nke gị.

Onyonyo Docker anyị nwere nrụnye MediaWiki na Wikibase zuru oke, yana usoro nrụnye nwere ike ịhazi ya ka ọ dabara mkpa gị.

Preparing your environment
Mezue nzọụkwụ ndị a niile tupu ịmalite itinye Wikibase.



Ntinye Docker
Na kọmputa ebe ị chọrọ ịgba ọsọ Wikibase, bu ụzọ tinye Docker.

Ọ bụrụ na ị chọrọ enyemaka ịwụnye karịa Docker's own instructions, ị nwere ike ịlele nkuzi ndị a maka Linux, Mac na Windows.



Lelee faịlụ
Lelee ebe nchekwa pipeline Wikibase site na GitHub iji nweta faịlụ nhazi ihe atụ. Ntinye ọhụrụ bụ $ 1, yabụ na-agba iwu ndị a:

git clone https://github.com/wmde/wikibase-release-pipeline cd wikibase-release-pipeline git checkout tags/wmde.13



Kwadebe faịlụ gị
Mepụta akwụkwọ ndekọ aha mmalite ọhụrụ nke ị ga-esi malite Docker. Buru n'uche aha nke ndekọ ahụ ga-apụta na aha akpa Docker gị. Maka ọmụmaatụ a, anyị ga-emepụta ndekọ aha "wbdocker'".

mkdir $HOME/wbdocker cp -r example/* $HOME/wbdocker cd $HOME/wbdocker mv template.env .env



Mee ka gburugburu ebe obibi gị dị iche iche
faịlụ $ 1 nwere mgbanwe gburugburu ebe obibi nke na-achịkwa ntinye Wikibase gị. Ị ga-adị mkpa idezi faịlụ a ma gbanwee ozi na ahịrị ụfọdụ dị ka ndị a:

MediaWiki Configuration

 * MW_ADMIN_NAME
 * MW_ADMIN_PASS
 * MW_ADMIN_EMAIL

These values define the username, password and email address of the administrative user in your new MediaWiki installation. You'll use this username and password to log into the web interface of your new instance for the first time; the email address you enter here will also allow you to reset your password if needed.



This secret key should be unique; MediaWiki uses it for several purposes (e.g., session management, fallback cryptographic entropy source). See the link for further information. To generate a random string for use in this file:

echo -n "MW_SECRET_KEY=" tr -dc 'A-Za-z0-9@#%^+_-' </dev/urandom | head -c 64 ; echo ''

Database Configuration

 * DB_NAME
 * DB_USER
 * DB_PASS

These values control the name of the database that MediaWiki will use, as well as the database username and password. At the bare minimum, change :

echo -n "DB_PASS=" tr -dc 'A-Za-z0-9@#%^+_-' </dev/urandom | head -c 32 ; echo ''

Wikibase Configuration

 * WIKIBASE_PINGBACK=false

By default, the Wikibase pingback feature is disabled. Please consider enabling this feature (which sends only anonymised data) by changing  to.

Enabling this feature significantly improves Wikimedia Deutschland's insight into how Wikibase is being used and helps us make more informed decisions regarding the development roadmap. For more information, read our pingback documentation topic.

Hostnames








These lines define the host name and port of your Wikibase (what you would put in your browser’s address bar) and, optionally, of the external services for an extended install.

Sandbox users (those who want only a locally accessible setup on a single computer) can and should leave this section untouched.

However, if you plan to use any of the above external services outside of a self-contained Docker setup, you need to set,  ,   and/or   to publicly accessible hostnames -- that is, hostnames that can be resolved in DNS -- or IP addresses. The latter might be the right choice if you're running this on a local network.

MAX_JOBS
You can specify that the job runner should run more jobs between restarts by setting  higher than its default value of 1. See below for more information on the job runner.

Installing and running Wikibase
Now that you've installed all the needed software and customised your environment file, you have one more choice: whether to perform a minimal install (just MediaWiki, a backing MySQL database and Wikibase) or an extended install (MediaWiki, database, Wikibase, WDQS, Elasticsearch, QuickStatements).

Minimal install
For a minimal install, in the launch directory where you copied and modified your files, simply run:

docker compose up -d

Extended install
For an extended install, in the launch directory where you copied and modified your files, run this extended command:

docker compose -f docker-compose.yml -f docker-compose.extra.yml up -d

Options
If you need to run multiple job runners, you can add the following option (with X being the number of job runners to run) onto your  command, as in this example:

docker compose up -d --scale wikibase_jobrunner=X

Up and running
You will now have at least two Docker containers running. To see your running containers, run. The following example output is from an extended install:

$ docker compose ps NAME                        COMMAND                   SERVICE              STATUS              PORTS wbdocker-elasticsearch-1       "/usr/local/bin/dock…"    elasticsearch        running             9300/tcp wbdocker-mysql-1               "docker-entrypoint.s…"    mysql                running             3306/tcp wbdocker-quickstatements-1     "/bin/bash /entrypoi…"    quickstatements      running             0.0.0.0:8840->80/tcp, :::8840->80/tcp wbdocker-wdqs-1                "/entrypoint.sh /run…"    wdqs                 running             9999/tcp wbdocker-wdqs-frontend-1       "/entrypoint.sh ngin…"    wdqs-frontend        running             0.0.0.0:8834->80/tcp, :::8834->80/tcp wbdocker-wdqs-proxy-1          "/bin/sh -c \"/entryp…"   wdqs-proxy           running             80/tcp wbdocker-wdqs-updater-1         "/entrypoint.sh /run…"    wdqs-updater         running             wbdocker-wikibase-1             "/bin/bash /entrypoi…"    wikibase             running             0.0.0.0:80->80/tcp, :::80->80/tcp wbdocker-wikibase_jobrunner-1   "/bin/bash /jobrunne…"    wikibase_jobrunner   running             80/tcp



For some more helpful Wikibase-oriented Docker commands, check out the Docker tooling section of our maintenance documentation.

Log into your new Wikibase by navigating to your local machine's web server.

Job runner
The example  sets up a dedicated job runner which restarts itself after every job, to ensure that changes to the configuration are picked up as quickly as possible.

If you run large batches of edits, this job runner may not be able to keep up with edits. You can speed it up by increasing the MAX_JOBS variable in your  file (see above), in order to run more jobs between restarts. This change won't take effect in the job runner until you restart your  project.

If you wish, you can also run several job runners in parallel by adding the option  to the   command. See the Installing section above.

Sitelinks
To create links between MediaWiki and Wikibase, run the add site script. You can learn more about adding sitelinks on the Wikidata sitelinks help page and the Wikibase advanced configuration page.

Using your new instance
Once all services have started, you can begin filling up, extending and customising your empty instance of Wikibase. Take a look at our setup resources page to get started.