public_git
/
bitnami-containers
mirror of https://github.com/bitnami/containers.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
bitnami-containers/bitnami/mediawiki/README.md

645 lines
28 KiB
Markdown
Raw Blame History

# MediaWiki packaged by Bitnami
## What is MediaWiki?
> MediaWiki is the free and open source wiki software that powers Wikipedia. Used by thousands of organizations, it is extremely powerful, scalable software and a feature-rich wiki implementation.
[Overview of MediaWiki](http://www.mediawiki.org/wiki/MediaWiki)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-mediawiki/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d
```
**Warning**: This quick setup is only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the [Environment Variables](#environment-variables) section for a more secure deployment.
## Why use Bitnami Images?
* Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
* With Bitnami images the latest bug fixes and features are available as soon as possible.
* Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
* All our images are based on [minideb](https://github.com/bitnami/minideb) a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading Linux distribution.
* All Bitnami images available in Docker Hub are signed with [Docker Content Trust (DCT)](https://docs.docker.com/engine/security/trust/content_trust/). You can use `DOCKER_CONTENT_TRUST=1` to verify the integrity of the images.
* Bitnami container images are released daily with the latest distribution packages available.
## How to deploy MediaWiki in Kubernetes?
Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami MediaWiki Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/mediawiki).
Bitnami containers can be used with [Kubeapps](https://kubeapps.com/) for deployment and management of Helm Charts in clusters.
## Why use a non-root container?
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://docs.bitnami.com/tutorials/work-with-non-root-containers/).
## Supported tags and respective `Dockerfile` links
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
* [`1`, `1-debian-10`, `1.37.2`, `1.37.2-debian-10-r52`, `latest` (1/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-mediawiki/blob/1.37.2-debian-10-r52/1/debian-10/Dockerfile)
Subscribe to project updates by watching the [bitnami/mediawiki GitHub repo](https://github.com/bitnami/bitnami-docker-mediawiki).
## Get this image
The recommended way to get the Bitnami MediaWiki Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/mediawiki).
```console
$ docker pull bitnami/mediawiki:latest
```
To use a specific version, you can pull a versioned tag. You can view the [list of available versions](https://hub.docker.com/r/bitnami/mediawiki/tags/) in the Docker Hub Registry.
```console
$ docker pull bitnami/mediawiki:[TAG]
```
If you wish, you can also build the image yourself.
```console
$ docker build -t bitnami/mediawiki:latest 'https://github.com/bitnami/bitnami-docker-mediawiki.git#master:1/debian-10'
```
## How to use this image
MediaWiki requires access to a MySQL or MariaDB database to store information. We'll use the [Bitnami Docker Image for MariaDB](https://www.github.com/bitnami/bitnami-docker-mariadb) for the database requirements.
### Run the application using Docker Compose
The main folder of this repository contains a functional [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-mediawiki/blob/master/docker-compose.yml) file. Run the application using it as shown below:
```console
$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-mediawiki/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d
```
### Using the Docker Command Line
If you want to run the application manually instead of using `docker-compose`, these are the basic steps you need to run:
#### Step 1: Create a network
```console
$ docker network create mediawiki-network
```
#### Step 2: Create a volume for MariaDB persistence and create a MariaDB container
```console
$ docker volume create --name mariadb_data
$ docker run -d --name mariadb \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MARIADB_USER=bn_mediawiki \
--env MARIADB_PASSWORD=bitnami \
--env MARIADB_DATABASE=bitnami_mediawiki \
--network mediawiki-network \
--volume mariadb_data:/bitnami/mariadb \
bitnami/mariadb:latest
```
#### Step 3: Create volumes for MediaWiki persistence and launch the container
```console
$ docker volume create --name mediawiki_data
$ docker run -d --name mediawiki \
-p 8080:8080 -p 8443:8443 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MEDIAWIKI_DATABASE_USER=bn_mediawiki \
--env MEDIAWIKI_DATABASE_PASSWORD=bitnami \
--env MEDIAWIKI_DATABASE_NAME=bitnami_mediawiki \
--network mediawiki-network \
--volume mediawiki_data:/bitnami/mediawiki \
bitnami/mediawiki:latest
```
Access your application at `http://your-ip/`
## Persisting your application
If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
For persistence you should mount a directory at the `/bitnami/mediawiki` path. If the mounted directory is empty, it will be initialized on the first run. Additionally you should mount a volume for persistence of the MariaDB data](https://github.com/bitnami/bitnami-docker-mariadb#persisting-your-database).
The above examples define the Docker volumes named mariadb_data and mediawiki_data. The MediaWiki application state will persist as long as volumes are not removed.
To avoid inadvertent removal of volumes, you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.
### Mount host directories as data volumes with Docker Compose
This requires a minor change to the [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-mediawiki/blob/master/docker-compose.yml) file present in this repository:
```diff
mariadb:
...
volumes:
- - 'mariadb_data:/bitnami/mariadb'
+ - /path/to/mariadb-persistence:/bitnami/mariadb
...
mediawiki:
...
volumes:
- - 'mediawiki_data:/bitnami/mediawiki'
+ - /path/to/mediawiki-persistence:/bitnami/mediawiki
...
-volumes:
- mariadb_data:
- driver: local
- mediawiki_data:
- driver: local
```
> NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
### Mount host directories as data volumes using the Docker command line
#### Step 1: Create a network (if it does not exist)
```console
$ docker network create mediawiki-network
```
#### Step 2. Create a MariaDB container with host volume
```console
$ docker run -d --name mariadb \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MARIADB_USER=bn_mediawiki \
--env MARIADB_PASSWORD=bitnami \
--env MARIADB_DATABASE=bitnami_mediawiki \
--network mediawiki-network \
--volume /path/to/mariadb-persistence:/bitnami/mariadb \
bitnami/mariadb:latest
```
#### Step 3. Create the MediaWiki container with host volumes
```console
$ docker run -d --name mediawiki \
-p 8080:8080 -p 8443:8443 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MEDIAWIKI_DATABASE_USER=bn_mediawiki \
--env MEDIAWIKI_DATABASE_PASSWORD=bitnami \
--env MEDIAWIKI_DATABASE_NAME=bitnami_mediawiki \
--network mediawiki-network \
--volume /path/to/mediawiki-persistence:/bitnami/mediawiki \
bitnami/mediawiki:latest
```
## Configuration
## Environment variables
When you start the MediaWiki image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the `docker run` command line. If you want to add a new environment variable:
* For docker-compose add the variable name and value under the application section in the [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-mediawiki/blob/master/docker-compose.yml) file present in this repository:
```yaml
mediawiki:
...
environment:
- MEDIAWIKI_PASSWORD=my_password
...
```
* For manual execution add a `--env` option with each variable and value:
```console
$ docker run -d --name mediawiki -p 80:8080 -p 443:8443 \
--env MEDIAWIKI_PASSWORD=my_password \
--network mediawiki-tier \
--volume /path/to/mediawiki-persistence:/bitnami/mediawiki \
bitnami/mediawiki:latest
```
Available variables:
##### User and Site configuration
- `MEDIAWIKI_USERNAME`: MediaWiki application username. Default: **user**
- `MEDIAWIKI_PASSWORD`: MediaWiki application password. Default: **bitnami123** (min 10 characters, alphanumeric, no special characters)
- `MEDIAWIKI_EMAIL`: MediaWiki application email. Default: **user@example.com**
- `MEDIAWIKI_WIKI_NAME`: MediaWiki wiki name. Default: **Bitnami MediaWiki**
- `MEDIAWIKI_HOST`: MediaWiki application host. No defaults.
- `MEDIAWIKI_EXTERNAL_HTTP_PORT_NUMBER`: Port to used by MediaWiki to generate URLs and links when accessing using HTTP. Default **80**.
- `MEDIAWIKI_EXTERNAL_HTTPS_PORT_NUMBER`: Port to used by MediaWiki to generate URLs and links when accessing using HTTPS. Default **443**.
- `MEDIAWIKI_ENABLE_HTTPS`: Whether to use HTTPS by default. Default: **no**.
##### Use an existing database
- `MEDIAWIKI_DATABASE_HOST`: Hostname for MariaDB server. Default: **mariadb**
- `MEDIAWIKI_DATABASE_PORT_NUMBER`: Port used by MariaDB server. Default: **3306**
- `MEDIAWIKI_DATABASE_NAME`: Database name that MediaWiki will use to connect with the database. Default: **bitnami_mediawiki**
- `MEDIAWIKI_DATABASE_USER`: Database user that MediaWiki will use to connect with the database. Default: **bn_mediawiki**
- `MEDIAWIKI_DATABASE_PASSWORD`: Database password that MediaWiki will use to connect with the database. No defaults.
- `ALLOW_EMPTY_PASSWORD`: It can be used to allow blank passwords. Default: **no**
##### Create a database for MediaWiki using mysql-client
- `MYSQL_CLIENT_FLAVOR`: SQL database flavor. Valid values: `mariadb` or `mysql`. Default: **mariadb**.
- `MYSQL_CLIENT_DATABASE_HOST`: Hostname for MariaDB server. Default: **mariadb**
- `MYSQL_CLIENT_DATABASE_PORT_NUMBER`: Port used by MariaDB server. Default: **3306**
- `MYSQL_CLIENT_DATABASE_ROOT_USER`: Database admin user. Default: **root**
- `MYSQL_CLIENT_DATABASE_ROOT_PASSWORD`: Database password for the database admin user. No defaults.
- `MYSQL_CLIENT_CREATE_DATABASE_NAME`: New database to be created by the mysql client module. No defaults.
- `MYSQL_CLIENT_CREATE_DATABASE_USER`: New database user to be created by the mysql client module. No defaults.
- `MYSQL_CLIENT_CREATE_DATABASE_PASSWORD`: Database password for the `MYSQL_CLIENT_CREATE_DATABASE_USER` user. No defaults.
- `MYSQL_CLIENT_CREATE_DATABASE_CHARACTER_SET`: Character set to use for the new database. No defaults.
- `MYSQL_CLIENT_CREATE_DATABASE_COLLATE`: Database collation to use for the new database. No defaults.
- `MYSQL_CLIENT_CREATE_DATABASE_PRIVILEGES`: Database privileges to grant for the user specified in `MYSQL_CLIENT_CREATE_DATABASE_USER` to the database specified in `MYSQL_CLIENT_CREATE_DATABASE_NAME`. No defaults.
- `MYSQL_CLIENT_ENABLE_SSL_WRAPPER`: Whether to force SSL connections to the database via the `mysql` CLI tool. Useful for applications that rely on the CLI instead of APIs. Default: **no**
- `MYSQL_CLIENT_ENABLE_SSL`: Whether to force SSL connections for the database. Default: **no**
- `MYSQL_CLIENT_SSL_CA_FILE`: Path to the SSL CA file for the new database. No defaults
- `MYSQL_CLIENT_SSL_CERT_FILE`: Path to the SSL CA file for the new database. No defaults
- `MYSQL_CLIENT_SSL_KEY_FILE`: Path to the SSL CA file for the new database. No defaults
- `ALLOW_EMPTY_PASSWORD`: It can be used to allow blank passwords. Default: **no**
##### SMTP Configuration
To configure MediaWiki to send email using SMTP you can set the following environment variables:
- `MEDIAWIKI_SMTP_HOST`: SMTP host.
- `MEDIAWIKI_SMTP_HOST_ID`: SMTP host ID. It is a MediaWiki-specific setting used to build the Message-ID email header. If not provided, it will default to the value of `MEDIAWIKI_SMTP_HOST`.
- `MEDIAWIKI_SMTP_PORT`: SMTP port.
- `MEDIAWIKI_SMTP_USER`: SMTP account user (if being used).
- `MEDIAWIKI_SMTP_PASSWORD`: SMTP account password (if being used).
- `MEDIAWIKI_ENABLE_SMTP_AUTH`: Whether to use authentication for SMTP server. Valid values: `yes`, `no`. Default: **yes**
##### PHP configuration
- `PHP_ENABLE_OPCACHE`: Enable OPcache for PHP scripts. No default.
- `PHP_EXPOSE_PHP`: Enables HTTP header with PHP version. No default.
- `PHP_MAX_EXECUTION_TIME`: Maximum execution time for PHP scripts. No default.
- `PHP_MAX_INPUT_TIME`: Maximum input time for PHP scripts. No default.
- `PHP_MAX_INPUT_VARS`: Maximum amount of input variables for PHP scripts. No default.
- `PHP_MEMORY_LIMIT`: Memory limit for PHP scripts. Default: **256M**
- `PHP_POST_MAX_SIZE`: Maximum size for PHP POST requests. No default.
- `PHP_UPLOAD_MAX_FILESIZE`: Maximum file size for PHP uploads. No default.
##### Example
This would be an example of SMTP configuration using a GMail account:
* Modify the [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-mediawiki/blob/master/docker-compose.yml) file present in this repository:
```yaml
mediawiki:
...
environment:
- MEDIAWIKI_DATABASE_USER=bn_mediawiki
- MEDIAWIKI_DATABASE_NAME=bitnami_mediawiki
- ALLOW_EMPTY_PASSWORD=yes
- MEDIAWIKI_SMTP_HOST=smtp.gmail.com
- MEDIAWIKI_SMTP_HOST_ID=mydomain.com
- MEDIAWIKI_SMTP_PORT=587
- MEDIAWIKI_SMTP_USER=your_email@gmail.com
- MEDIAWIKI_SMTP_PASSWORD=your_password
...
```
* For manual execution:
```console
$ docker run -d --name mediawiki -p 80:8080 -p 443:8443 \
--env MEDIAWIKI_DATABASE_USER=bn_mediawiki \
--env MEDIAWIKI_DATABASE_NAME=bitnami_mediawiki \
--env MEDIAWIKI_SMTP_HOST=smtp.gmail.com \
--env MEDIAWIKI_SMTP_HOST_ID=mydomain.com \
--env MEDIAWIKI_SMTP_PORT=587 \
--env MEDIAWIKI_SMTP_USER=your_email@gmail.com \
--env MEDIAWIKI_SMTP_PASSWORD=your_password \
--network mediawiki-tier \
--volume /path/to/mediawiki-persistence:/bitnami/mediawiki \
bitnami/mediawiki:latest
```
# How to install imagemagick in the Bitnami MediaWiki Docker image
If you require better quality thumbnails for your uploaded images, you may want to install imagemagick instead of using GD. To do so you can build your own docker image adding the `imagemagick` system package. Since we are using a non-root container, we have to swap the user to root to install imagemagick and it's requirements.
1. Create the following Dockerfile
```Dockerfile
FROM bitnami/mediawiki:latest
USER root
RUN install_packages imagemagick
USER 1001
```
2. Build the docker image
```console
$ docker build -t bitnami/mediawiki:imagemagick .
```
3. Edit the *docker-compose.yml* to use the docker image built in the previous step.
4. Finally exec into your MediaWiki container and edit the file */opt/bitnami/mediawiki/LocalSettings.php* as described [here](https://www.mediawiki.org/wiki/Manual:Installing_third-party_tools#Image_thumbnailing) in order to start using imagemagick.
# How to migrate from a Bitnami MediaWiki Stack
You can follow these steps in order to migrate it to this container:
1. Export the data from your SOURCE installation: (assuming an installation in `/opt/bitnami` directory)
```console
$ mysqldump -u root -p bitnami_mediawiki > ~/backup-mediawiki-database.sql
$ gzip -c ~/backup-mediawiki-database.sql > ~/backup-mediawiki-database.sql.gz
$ cd /opt/bitnami/apps/mediawiki/htdocs/
$ tar cfz ~/backup-mediawiki-extensions.tar.gz extensions
$ tar cfz ~/backup-mediawiki-images.tar.gz images
$ tar cfz ~/backup-mediawiki-skins.tar.gz skins
```
2. Copy the backup files to your TARGET installation:
```console
$ scp ~/backup-mediawiki-* YOUR_USERNAME@TARGET_HOST:~
```
3. Create the MediaWiki Container as described in the section [How to use this Image (Using Docker Compose)](https://github.com/bitnami/bitnami-docker-mediawiki#using-docker-compose)
4. Wait for the initial setup to finish. You can follow it with
```console
$ docker-compose logs -f mediawiki
```
and press `Ctrl-C` when you see this:
```console
nami INFO mediawiki successfully initialized
Starting mediawiki ...
```
5. Stop Apache:
```console
$ docker-compose exec mediawiki nami stop apache
```
6. Obtain the password used by MediaWiki to access the database in order avoid reconfiguring it:
```console
$ docker-compose exec mediawiki bash -c 'cat /opt/bitnami/mediawiki/LocalSettings.php | grep wgDBpassword'
```
7. Restore the database backup: (replace ROOT_PASSWORD below with your MariaDB root password)
```console
$ cd ~
$ docker-compose exec mariadb mysql -u root -pROOT_PASSWORD
$ MariaDB [(none)]> drop database bitnami_mediawiki;
$ MariaDB [(none)]> create database bitnami_mediawiki;
$ MariaDB [(none)]> grant all privileges on bitnami_mediawiki.* to 'bn_mediawiki'@'%' identified by 'PASSWORD_OBTAINED_IN_STEP_6';
$ MariaDB [(none)]> exit
$ gunzip -c ./backup-mediawiki-database.sql.gz | docker exec -i $(docker-compose ps -q mariadb) mysql -u root bitnami_mediawiki -pROOT_PASSWORD
```
8. Restore extensions/images/skins directories from backup:
```console
$ cat ./backup-mediawiki-extensions.tar.gz | docker exec -i $(docker-compose ps -q mediawiki) bash -c 'cd /bitnami/mediawiki/ ; tar -xzvf -'
$ cat ./backup-mediawiki-images.tar.gz | docker exec -i $(docker-compose ps -q mediawiki) bash -c 'cd /bitnami/mediawiki/ ; tar -xzvf -'
$ cat ./backup-mediawiki-skins.tar.gz | docker exec -i $(docker-compose ps -q mediawiki) bash -c 'cd /bitnami/mediawiki/ ; tar -xzvf -'
```
9. Fix MediaWiki directory permissions:
```console
$ docker-compose exec mediawiki chown -R daemon:daemon /bitnami/mediawiki
```
10. Restart Apache:
```console
$ docker-compose exec mediawiki nami start apache
```
## Logging
The Bitnami MediaWiki Docker image sends the container logs to `stdout`. To view the logs:
```console
$ docker logs mediawiki
```
Or using Docker Compose:
```console
$ docker-compose logs mediawiki
```
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## Maintenance
### Backing up your container
To backup your data, configuration and logs, follow these simple steps:
#### Step 1: Stop the currently running container
```console
$ docker stop mediawiki
```
Or using Docker Compose:
```console
$ docker-compose stop mediawiki
```
#### Step 2: Run the backup command
We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.
```console
$ docker run --rm -v /path/to/mediawiki-backups:/backups --volumes-from mediawiki busybox \
cp -a /bitnami/mediawiki /backups/latest
```
### Restoring a backup
Restoring a backup is as simple as mounting the backup as volumes in the containers.
For the MariaDB database container:
```diff
$ docker run -d --name mariadb \
...
- --volume /path/to/mariadb-persistence:/bitnami/mariadb \
+ --volume /path/to/mariadb-backups/latest:/bitnami/mariadb \
bitnami/mariadb:latest
```
For the MediaWiki container:
```diff
$ docker run -d --name mediawiki \
...
- --volume /path/to/mediawiki-persistence:/bitnami/mediawiki \
+ --volume /path/to/mediawiki-backups/latest:/bitnami/mediawiki \
bitnami/mediawiki:latest
```
### Upgrade this image
Bitnami provides up-to-date versions of MariaDB and MediaWiki, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the MediaWiki container. For the MariaDB upgrade see: https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#upgrade-this-image
#### Step 1: Get the updated image
```console
$ docker pull bitnami/mediawiki:latest
```
#### Step 2: Stop the running container
Stop the currently running container using the following command:
```console
$ docker-compose stop mediawiki
```
#### Step 3: Take a snapshot of the application state
Follow the steps in [Backing up your container](#backing-up-your-container) to take a snapshot of the current application state.
#### Step 4: Remove the currently running container
Remove the currently running container by executing the following command:
```consolee
docker-compose rm -v mediawiki
```
#### Step 5: Run the new image
Update the image tag in `docker-compose.yml` and re-create your container with the new image:
```console
$ docker-compose up -d
```
## Customize this image
The Bitnami MediaWiki Docker image is designed to be extended so it can be used as the base image for your custom web applications.
### Extend this image
Before extending this image, please note there are certain configuration settings you can modify using the original image:
- Settings that can be adapted using environment variables. For instance, you can change the ports used by Apache for HTTP and HTTPS, by setting the environment variables `APACHE_HTTP_PORT_NUMBER` and `APACHE_HTTPS_PORT_NUMBER` respectively.
- [Adding custom virtual hosts](https://github.com/bitnami/bitnami-docker-apache#adding-custom-virtual-hosts).
- [Replacing the 'httpd.conf' file](https://github.com/bitnami/bitnami-docker-apache#full-configuration).
- [Using custom SSL certificates](https://github.com/bitnami/bitnami-docker-apache#using-custom-ssl-certificates).
If your desired customizations cannot be covered using the methods mentioned above, extend the image. To do so, create your own image using a Dockerfile with the format below:
```Dockerfile
FROM bitnami/mediawiki
## Put your customizations below
...
```
Here is an example of extending the image with the following modifications:
- Install the `vim` editor
- Modify the Apache configuration file
- Modify the ports used by Apache
```Dockerfile
FROM bitnami/mediawiki
LABEL maintainer "Bitnami <containers@bitnami.com>"
## Change user to perform privileged actions
USER 0
## Install 'vim'
RUN install_packages vim
## Revert to the original non-root user
USER 1001
## Enable mod_ratelimit module
RUN sed -i -r 's/#LoadModule ratelimit_module/LoadModule ratelimit_module/' /opt/bitnami/apache/conf/httpd.conf
## Modify the ports used by Apache by default
# It is also possible to change these environment variables at runtime
ENV APACHE_HTTP_PORT_NUMBER=8181
ENV APACHE_HTTPS_PORT_NUMBER=8143
EXPOSE 8181 8143
```
Based on the extended image, you can update the [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-mediawiki/blob/master/docker-compose.yml) file present in this repository to add other features:
```diff
mediawiki:
- image: bitnami/mediawiki:latest
+ build: .
ports:
- - '80:8080'
- - '443:8443'
+ - '80:8181'
+ - '443:8143'
environment:
+ - PHP_MEMORY_LIMIT=512m
...
```
# Notable Changes
## 1.34.2-debian-10-r5
- The size of the container image has been decreased.
- The configuration logic is now based on Bash scripts in the *rootfs/* folder.
- The MediaWiki container image has been migrated to a "non-root" user approach. Previously the container ran as the `root` user and the Apache daemon was started as the `daemon` user. From now on, both the container and the Apache daemon run as user `1001`. You can revert this behavior by changing `USER 1001` to `USER root` in the Dockerfile, or `user: root` in `docker-compose.yml`. Consequences:
- The HTTP/HTTPS ports exposed by the container are now `8080/8443` instead of `80/443`.
- Backwards compatibility is not guaranteed when data is persisted using docker or docker-compose. We highly recommend migrating the MediaWiki site by exporting its content, and importing it on a new MediaWiki container. Follow the steps in [Backing up your container](#backing-up-your-container) and [Restoring a backup](#restoring-a-backup) to migrate the data between the old and new container.
## 1.32.1-debian-9-r20 and 1.32.1-ol-7-r33
- This image has been adapted so it's easier to customize. See the [Customize this image](#customize-this-image) section for more information.
- The Apache configuration volume (`/bitnami/apache`) has been deprecated, and support for this feature will be dropped in the near future. Until then, the container will enable the Apache configuration from that volume if it exists. By default, and if the configuration volume does not exist, the configuration files will be regenerated each time the container is created. Users wanting to apply custom Apache configuration files are advised to mount a volume for the configuration at `/opt/bitnami/apache/conf`, or mount specific configuration files individually.
- The PHP configuration volume (`/bitnami/php`) has been deprecated, and support for this feature will be dropped in the near future. Until then, the container will enable the PHP configuration from that volume if it exists. By default, and if the configuration volume does not exist, the configuration files will be regenerated each time the container is created. Users wanting to apply custom PHP configuration files are advised to mount a volume for the configuration at `/opt/bitnami/php/conf`, or mount specific configuration files individually.
- Enabling custom Apache certificates by placing them at `/opt/bitnami/apache/certs` has been deprecated, and support for this functionality will be dropped in the near future. Users wanting to enable custom certificates are advised to mount their certificate files on top of the preconfigured ones at `/certs`.
## Contributing
We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/bitnami-docker-mediawiki/issues), or submit a [pull request](https://github.com/bitnami/bitnami-docker-mediawiki/pulls) with your contribution.
## Issues
If you encountered a problem running this container, you can file an [issue](https://github.com/bitnami/bitnami-docker-mediawiki/issues/new). Be sure to include the following information in your issue:
- Host OS and version
- Docker version (`docker version`)
- Output of `docker info`
- Version of this container
- The command you used to run the container, and any relevant output you saw (masking any sensitive information)
### Community supported solution
Please, note this asset is a community-supported solution. This means that the Bitnami team is not actively working on new features/improvements nor providing support through GitHub Issues. Any new issue will stay open for 20 days to allow the community to contribute, after 15 days without activity the issue will be marked as stale being closed after 5 days.
The Bitnami team will review any PR that is created, feel free to create a PR if you find any issue or want to implement a new feature.
New versions and releases cadence are not going to be affected. Once a new version is released in the upstream project, the Bitnami container image will be updated to use the latest version, supporting the different branches supported by the upstream project as usual.
## License
Copyright &copy; 2022 Bitnami
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Reference in New Issue View Git Blame Copy Permalink