What is WordPress with NGINX?

WordPress with NGINX combines the most popular blogging application with the power of the NGINX web server.

https://www.wordpress.org/ https://nginx.org/

TL;DR;

Docker Compose

$ git clone https://github.com/bitnami/bitnami-docker-wordpress-nginx
$ cd bitnami-docker-wordpress-nginx/4
$ docker-compose up

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.

Supported tags and respective `Dockerfile` links

NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8.

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

Subscribe to project updates by watching the bitnami/wordpress-nginx GitHub repo.

Prerequisites

To run this application you need Docker Engine >= 1.10.0. Docker Compose is recommended with a version 1.6.0 or later.

How to use this image

WordPress requires access to a MySQL or MariaDB database to store information. We'll use our very own MariaDB image for the database requirements.

Using Docker Compose

The recommended way to run WordPress is using Docker Compose using the docker-compose.yml file that you can find into the different directories, depending on the distro you want to use.

Launch the containers using:

$ 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:

Create a network

$ docker network create wordpress-tier

Create a volume for MariaDB persistence and create a MariaDB container

$ docker volume create --name mariadb_data
$ docker run -d --name mariadb \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e MARIADB_USER=bn_wordpress \
  -e MARIADB_DATABASE=bitnami_wordpress \
  --net wordpress-tier \
  --volume mariadb_data:/bitnami \
  bitnami/mariadb:latest

Create volumes for WordPress persistence and launch the container

$ docker volume create --name wordpress_data
$ docker run -d --name wordpress -p 80:80 -p 443:443 \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e WORDPRESS_DATABASE_USER=bn_wordpress \
  -e WORDPRESS_DATABASE_NAME=bitnami_wordpress \
  --net wordpress-tier \
  --volume wordpress_data:/bitnami \
  --volume ./wordpress-vhosts.conf:/bitnami/nginx/conf/vhosts/wordpress-vhosts.conf \
  bitnami/wordpress-nginx:latest

Access your application at http://your-ip/

Persisting your application

If you remove the container all your data and configurations 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 volume at the /bitnami path. Additionally you should mount a volume for persistence of the MariaDB data.

The above examples define docker volumes namely mariadb_data and wordpress_data. The Wordpress application state will persist as long as these volumes are not removed.

To avoid inadvertent removal of these 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

The following docker-compose.yml template demonstrates the use of host directories as data volumes.

version: '2'

services:
  mariadb:
    image: 'bitnami/mariadb:latest'
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
      - MARIADB_USER=bn_wordpress
      - MARIADB_DATABASE=bitnami_wordpress
    volumes:
      - /path/to/mariadb-persistence:/bitnami
  wordpress:
    image: bitnami/wordpress-nginx:latest-rhel-7
    depends_on:
      - mariadb
    ports:
      - '80:80'
      - '443:443'
    environment:
      - WORDPRESS_DATABASE_USER=bn_wordpress
      - WORDPRESS_DATABASE_NAME=bitnami_wordpress
      - ALLOW_EMPTY_PASSWORD=yes
    volumes:
      - /path/to/wordpress-persistence:/bitnami
      - ./wordpress-vhosts.conf:/bitnami/nginx/conf/vhosts/wordpress-vhosts.conf

Upgrading WordPress

Bitnami provides up-to-date versions of MariaDB and WordPress, 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 WordPress container. For the MariaDB upgrade see https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#upgrade-this-image

The bitnami/wordpress-nginx:latest tag always points to the most recent release. To get the most recent release you can simple repull the latest tag from the Docker Hub with docker pull bitnami/wordpress-nginx:latest. However it is recommended to use tagged versions.

Get the updated images:

$ docker pull bitnami/wordpress-nginx:latest

Stop your container

For docker-compose: $ docker-compose stop wordpress
For manual execution: $ docker stop wordpress

Take a snapshot of the application state

$ rsync -a /path/to/wordpress-persistence /path/to/wordpress-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

Additionally, snapshot the MariaDB data

You can use these snapshots to restore the application state should the upgrade fail.

Remove the stopped container

For docker-compose: $ docker-compose rm wordpress
For manual execution: $ docker rm wordpress

Run the new image

For docker-compose: $ docker-compose start wordpress
For manual execution (mount the directories if needed): docker run --name wordpress bitnami/wordpress-nginx:latest

Configuration

Environment variables

The WordPress instance can be customized by specifying environment variables on the first run. The following environment values are provided to custom WordPress:

User and Site configuration

WORDPRESS_USERNAME: WordPress application username. Default: user
WORDPRESS_PASSWORD: WordPress application password. Default: bitnami
WORDPRESS_EMAIL: WordPress application email. Default: [email protected]
WORDPRESS_FIRST_NAME: WordPress user first name. Default: FirstName
WORDPRESS_LAST_NAME: WordPress user last name. Default: LastName
WORDPRESS_BLOG_NAME: WordPress blog name. Default: User's blog

Use an existing database

MARIADB_HOST: Hostname for MariaDB server. Default: mariadb
MARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306
WORDPRESS_DATABASE_NAME: Database name that WordPress will use to connect with the database. Default: bitnami_wordpress
WORDPRESS_TABLE_PREFIX: Table prefix to use in WordPress. Default: wp_
WORDPRESS_DATABASE_USER: Database user that WordPress will use to connect with the database. Default: bn_wordpress
WORDPRESS_DATABASE_PASSWORD: Database password that WordPress 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 WordPress using mysql-client

MARIADB_HOST: Hostname for MariaDB server. Default: mariadb
MARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306
MARIADB_ROOT_USER: Database admin user. Default: root
MARIADB_ROOT_PASSWORD: Database password for the MARIADB_ROOT_USER user. No defaults.
MYSQL_CLIENT_CREATE_DATABASE_NAME: New database to be created by the mysql client module. No defaults.
WORDPRESS_TABLE_PREFIX: Table prefix to use in WordPress. Default: wp_
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.
ALLOW_EMPTY_PASSWORD: It can be used to allow blank passwords. Default: no

SMTP Configuration

To configure WordPress to send email using SMTP you can set the following environment variables:

SMTP_HOST: Host for outgoing SMTP email. No defaults.
SMTP_PORT: Port for outgoing SMTP email. No defaults.
SMTP_USER: User of SMTP used for authentication (likely email). No defaults.
SMTP_PASSWORD: Password for SMTP. No defaults.
SMTP_PROTOCOL: Secure connection protocol to use for SMTP [tls, ssl, none]. No defaults.

This would be an example of SMTP configuration using a GMail account:

docker-compose (application part):

  wordpress:
    image: bitnami/wordpress-nginx:latest-rhel-7
    ports:
      - 80:80
      - 443:443
    environment:
      - MARIADB_HOST=mariadb
      - MARIADB_PORT_NUMBER=3306
      - WORDPRESS_DATABASE_USER=bn_wordpress
      - WORDPRESS_DATABASE_NAME=bitnami_wordpress
      - SMTP_HOST=smtp.gmail.com
      - SMTP_PORT=587
      - [email protected]
      - SMTP_PASSWORD=your_password
      - SMTP_PROTOCOL=tls
    volumes:
      - wordpress_data:/bitnami/wordpress-nginx
      - ./wordpress-vhosts.conf:/bitnami/nginx/conf/vhosts/wordpress-vhosts.conf

For manual execution:

$ docker run -d --name wordpress -p 80:80 -p 443:443 \
  --net wordpress-tier \
  --env SMTP_HOST=smtp.gmail.com --env SMTP_PORT=587 \
  --env [email protected] --env SMTP_PASSWORD=your_password \
  --env ALLOW_EMPTY_PASSWORD=yes --env WORDPRESS_DATABASE_USER=bn_wordpress \
  --env WORDPRESS_DATABASE_NAME=bitnami_wordpress \
  --volume wordpress_data:/bitnami/wordpress-nginx \
  --volume ./wordpress-vhosts.conf:/bitnami/nginx/conf/vhosts/wordpress-vhosts.conf \
  bitnami/wordpress-nginx:latest

Connect WordPress docker container to an existing database

The Bitnami WordPress container supports connecting the WordPress application to an external database. In order to configure it, you should set the following environment variables:

MARIADB_HOST: Hostname for MariaDB server. Default: mariadb
MARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306
WORDPRESS_DATABASE_NAME: Database name that WordPress will use to connect with the database. Default: bitnami_wordpress
WORDPRESS_DATABASE_USER: Database user that WordPress will use to connect with the database. Default: bn_wordpress
WORDPRESS_DATABASE_PASSWORD: Database password that WordPress will use to connect with the database. No defaults.

This would be an example of using an external database for WordPress.

docker-compose:

  wordpress:
    image: bitnami/wordpress-nginx:latest
    ports:
      - 80:80
      - 443:443
    environment:
      - MARIADB_HOST=mariadb_host
      - MARIADB_PORT_NUMBER=3306
      - WORDPRESS_DATABASE_NAME=wordpress_db
      - WORDPRESS_DATABASE_USER=wordpress_user
      - WORDPRESS_DATABASE_PASSWORD=wordpress_password
    volumes:
      - wordpress_data:/bitnami
      - ./wordpress-vhosts.conf:/bitnami/nginx/conf/vhosts/wordpress-vhosts.conf

For manual execution:

$ docker run -d --name wordpress -p 80:80 -p 443:443 \
  --net wordpress-tier \
  --env MARIADB_HOST=mariadb_host \
  --env MARIADB_PORT_NUMBER=3306 \
  --env WORDPRESS_DATABASE_NAME=wordpress_db \
  --env WORDPRESS_DATABASE_USER=wordpress_user \
  --env WORDPRESS_DATABASE_PASSWORD=wordpress_password \
  --volume wordpress_data:/bitnami \
  --volume ./wordpress-vhosts.conf:/bitnami/nginx/conf/vhosts/wordpress-vhosts.conf \
  bitnami/wordpress-nginx:latest

Contributing

We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.

Issues

If you encountered a problem running this container, you can file an issue. For us to provide better support, 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 ($ echo $BITNAMI_IMAGE_VERSION inside the container)
The command you used to run the container, and any relevant output you saw (masking any sensitive information)

License

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.

Name		Name	Last commit message	Last commit date
Latest commit History 207 Commits
.github		.github
4-php5		4-php5
4		4
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md
circle.yml		circle.yml

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

What is WordPress with NGINX?

TL;DR;

Docker Compose

Why use Bitnami Images?

Supported tags and respective `Dockerfile` links

Prerequisites

How to use this image

Using Docker Compose

Using the Docker Command Line

Persisting your application

Mount host directories as data volumes with Docker Compose

Upgrading WordPress

Configuration

Environment variables

User and Site configuration

Use an existing database

Create a database for WordPress using mysql-client

SMTP Configuration

Connect WordPress docker container to an existing database

Contributing

Issues

License

About

Releases

Packages

Languages

License

tejdeepsingh/bitnami-docker-wordpress-nginx

Folders and files

Latest commit

History

Repository files navigation

What is WordPress with NGINX?

TL;DR;

Docker Compose

Why use Bitnami Images?

Supported tags and respective Dockerfile links

Prerequisites

How to use this image

Using Docker Compose

Using the Docker Command Line

Persisting your application

Mount host directories as data volumes with Docker Compose

Upgrading WordPress

Configuration

Environment variables

User and Site configuration

Use an existing database

Create a database for WordPress using mysql-client

SMTP Configuration

Connect WordPress docker container to an existing database

Contributing

Issues

License

About

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Languages

Supported tags and respective `Dockerfile` links

Packages