Self-host MediaWiki with Levelrail

The wiki engine behind Wikipedia, for large collaborative knowledge bases with rich version history.

  • Memory512 MiB
  • Archarm64
  • Services2

How to self-host MediaWiki

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • postgres:16-alpine
    • mediawiki:1.43
  2. Create the app

    2 services start in a single Compose app, with 2 named volume mounts for your data, on port 80.

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 2 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

MediaWiki requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
80
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
not yet recorded
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then MediaWiki. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the MediaWiki docs page.

Deploy MediaWiki your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy MediaWiki from the CLI

levelrail-cli templates deploy mediawiki --name my-mediawiki

Deploy MediaWiki with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/mediawiki/deploy

MediaWiki configuration

MediaWiki services

ServiceImagePortsVolumes
db postgres:16-alpine none mediawiki_db_data -> /var/lib/postgresql/data
mediawiki mediawiki:1.43 80 mediawiki_images -> /var/www/html/images

MediaWiki environment variables

VariableServiceValue
POSTGRES_DB db Preset by the template
POSTGRES_PASSWORD db Generated at deploy
POSTGRES_USER db Preset by the template

Ports and volumes

Ports
80
Volumes
2 named mounts: mediawiki_db_data -> /var/lib/postgresql/data, mediawiki_images -> /var/www/html/images

MediaWiki FAQ

How much memory does MediaWiki need?

The catalog lists about 512 MiB of memory for MediaWiki across its 2 services.

Does MediaWiki run on arm64?

For MediaWiki, an arm64 image is published; amd64 is image published.

Does MediaWiki need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does MediaWiki bundle?

The template includes Postgres, running as its own service.

Which ports does MediaWiki use?

MediaWiki listens on port 80 inside the stack.

Where does MediaWiki keep its data?

In named volumes: mediawiki_db_data mounted at /var/lib/postgresql/data and mediawiki_images mounted at /var/www/html/images.

Can I deploy MediaWiki on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for MediaWiki, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, mediawiki:1.43 is what you deploy there.

levelrail-cli templates deploy mediawiki --name my-mediawiki