History

Bitnami Bot 15c21b9547 5.9.3-debian-10-r52 release		2022-05-25 03:05:57 +00:00
..
5/debian-10	5.9.3-debian-10-r51 release	2022-05-24 03:00:29 +00:00
README.md	5.9.3-debian-10-r52 release	2022-05-25 03:05:57 +00:00
docker-compose.yml	…

README.md

WordPress for Intel packaged by Bitnami

What is WordPress for Intel?

WordPress for Intel is the most popular blogging application combined with cryptography acceleration for 3rd gen Xeon Scalable Processors (Ice Lake) to get a breakthrough performance improvement.

Overview of WordPress for Intel

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

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-wordpress-intel/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 section for a more secure deployment.

Why use Intel optimized containers

Encryption is becoming pervasive with most organizations increasingly adopting encryption for application execution, data in flight, and data storage. Intel® 3rd gen Xeon® Scalable Processor (Ice Lake) cores and architecture, offers several new instructions for encryption acceleration. These new instructions, coupled with algorithmic and software innovations, deliver breakthrough performance for the industry's most widely deployed cryptographic ciphers.

This solution accelerates the processing of the Transport Layer Security (TLS) significantly by using built-in Intel crypto acceleration included in the latest Intel 3rd gen Xeon Scalable Processor (Ice Lake). For more information, refer to Intel’s documentation.

It requires a 3rd gen Xeon Scalable Processor (Ice Lake) to get a breakthrough performance improvement.

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 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). 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 WordPress for Intel 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 WordPress for Intel Chart GitHub repository.

Bitnami containers can be used with Kubeapps 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.

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.

5, 5-debian-10, 5.9.3, 5.9.3-debian-10-r52, latest (5/debian-10/Dockerfile)

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

Get this image

The recommended way to get the Bitnami WordPress for Intel Docker Image is to pull the prebuilt image from the Docker Hub Registry.

$ docker pull bitnami/wordpress-intel:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

$ docker pull bitnami/wordpress-intel:[TAG]

If you wish, you can also build the image yourself.

$ docker build -t bitnami/wordpress-intel:latest 'https://github.com/bitnami/bitnami-docker-wordpress.git#master:5/debian-10'

How to use this image

WordPress for Intel requires access to a MySQL or MariaDB database to store information. We'll use the Bitnami Docker Image for MariaDB for the database requirements.

Run the application using Docker Compose

The main folder of this repository contains a functional docker-compose.yml file. Run the application using it as shown below:

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-wordpress-intel/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

$ docker network create wordpress-network

Step 2: Create a volume for MariaDB persistence and create a MariaDB container

$ docker volume create --name mariadb_data
$ docker run -d --name mariadb \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env MARIADB_USER=bn_wordpress \
  --env MARIADB_PASSWORD=bitnami \
  --env MARIADB_DATABASE=bitnami_wordpress \
  --network wordpress-network \
  --volume mariadb_data:/bitnami/mariadb \
  bitnami/mariadb:latest

Step 3: Create volumes for WordPress for Intel persistence and launch the container

$ docker volume create --name wordpress_data
$ docker run -d --name wordpress \
  -p 8080:8080 -p 8443:8443 \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env WORDPRESS_DATABASE_USER=bn_wordpress \
  --env WORDPRESS_DATABASE_PASSWORD=bitnami \
  --env WORDPRESS_DATABASE_NAME=bitnami_wordpress \
  --network wordpress-network \
  --volume wordpress_data:/bitnami/wordpress \
  bitnami/wordpress-intel: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/wordpress 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.

The above examples define the Docker volumes named mariadb_data and wordpress_data. The WordPress for Intel 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 file present in this repository:

   mariadb:
     ...
     volumes:
-      - 'mariadb_data:/bitnami/mariadb'
+      - /path/to/mariadb-persistence:/bitnami/mariadb
   ...
   wordpress:
     ...
     volumes:
-      - 'wordpress_data:/bitnami/wordpress'
+      - /path/to/wordpress-persistence:/bitnami/wordpress
   ...
-volumes:
-  mariadb_data:
-    driver: local
-  wordpress_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)

$ docker network create wordpress-network

Step 2. Create a MariaDB container with host volume

$ docker run -d --name mariadb \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env MARIADB_USER=bn_wordpress \
  --env MARIADB_PASSWORD=bitnami \
  --env MARIADB_DATABASE=bitnami_wordpress \
  --network wordpress-network \
  --volume /path/to/mariadb-persistence:/bitnami/mariadb \
  bitnami/mariadb:latest

NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID 1001.

Step 3. Create the WordPress for Intel container with host volumes

$ docker run -d --name wordpress \
  -p 8080:8080 -p 8443:8443 \
  --env ALLOW_EMPTY_PASSWORD=yes \
  --env WORDPRESS_DATABASE_USER=bn_wordpress \
  --env WORDPRESS_DATABASE_PASSWORD=bitnami \
  --env WORDPRESS_DATABASE_NAME=bitnami_wordpress \
  --network wordpress-network \
  --volume /path/to/wordpress-persistence:/bitnami/wordpress \
  bitnami/wordpress-intel:latest

NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID 1001.

Configuration

Environment variables

When you start the WordPress for Intel 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. Please note that some variables are only considered when the container is started for the first time. 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 file present in this repository:
```
wordpress:
  ...
  environment:
    - WORDPRESS_PASSWORD=my_password
  ...
```

For manual execution add a --env option with each variable and value:

$ docker run -d --name wordpress -p 80:8080 -p 443:8443 \
  --env WORDPRESS_PASSWORD=my_password \
  --network wordpress-tier \
  --volume /path/to/wordpress-persistence:/bitnami \
  bitnami/wordpress-intel:latest

Available environment variables:

User and Site configuration

NGINX_HTTP_PORT_NUMBER: Port used by Nginx for HTTP. Default: 8080
NGINX_HTTPS_PORT_NUMBER: Port used by Nginx for HTTPS. Default: 8443
WORDPRESS_USERNAME: WordPress for Intel application username. Default: user
WORDPRESS_PASSWORD: WordPress for Intel application password. Default: bitnami
WORDPRESS_EMAIL: WordPress for Intel application email. Default: user@example.com
WORDPRESS_FIRST_NAME: WordPress for Intel user first name. Default: FirstName
WORDPRESS_LAST_NAME: WordPress for Intel user last name. Default: LastName
WORDPRESS_BLOG_NAME: WordPress for Intel blog name. Default: User's blog
WORDPRESS_DATA_TO_PERSIST: Space separated list of files and directories to persist. Use a space to persist no data: " ". Default: "wp-config.php wp-content"
WORDPRESS_RESET_DATA_PERMISSIONS: Force resetting ownership/permissions on persisted data when restarting WordPress for Intel, otherwise it assumes the ownership/permissions are correct. Ignored when running as non-root. Default: no
WORDPRESS_TABLE_PREFIX: Table prefix to use in WordPress for Intel. Default: wp_
WORDPRESS_PLUGINS: List of WordPress for Intel plugins to install and activate, separated via commas. Can also be set to all to activate all currently installed plugins, or none to skip. Default: none
WORDPRESS_EXTRA_INSTALL_ARGS: Extra flags to append to the WordPress for Intel 'wp core install' command call. No defaults.
WORDPRESS_EXTRA_CLI_ARGS: Extra flags to append to all WP-CLI command calls. No defaults.
WORDPRESS_EXTRA_WP_CONFIG_CONTENT: Extra configuration to append to wp-config.php during install. No defaults.
WORDPRESS_ENABLE_HTTPS: Whether to use HTTPS by default. Default: no
WORDPRESS_SKIP_BOOTSTRAP: Skip the WordPress for Intel installation wizard. This is necessary when providing a database with existing WordPress for Intel data. Default: no
WORDPRESS_AUTO_UPDATE_LEVEL: Level of auto-updates to allow for the WordPress for Intel core installation. Valid values: major, minor, none. Default: none

Multisite configuration

WORDPRESS_ENABLE_MULTISITE: Enable WordPress for Intel Multisite configuration. Default: no
WORDPRESS_MULTISITE_HOST: WordPress for Intel hostname/address. Only used for Multisite installations. No defaults.
WORDPRESS_MULTISITE_EXTERNAL_HTTP_PORT_NUMBER: Port to used by WordPress for Intel to generate URLs and links when accessing using HTTP. Will be ignored if multisite mode is not enabled. Default 80
WORDPRESS_MULTISITE_EXTERNAL_HTTPS_PORT_NUMBER: Port to used by WordPress for Intel to generate URLs and links when accessing using HTTPS. Will be ignored if multisite mode is not enabled. Default 443
WORDPRESS_MULTISITE_NETWORK_TYPE: WordPress for Intel Multisite network type to enable. Valid values: subfolder, subdirectory, subdomain. Default: subdomain
WORDPRESS_MULTISITE_ENABLE_NIP_IO_REDIRECTION: Whether to enable IP address redirection to nip.io wildcard DNS when enabling WordPress for Intel Multisite. This is useful when running on an IP address with subdomain network type. Default: no
WORDPRESS_MULTISITE_FILEUPLOAD_MAXK: Maximum upload file size allowed for WordPress for Intel Multisite uploads, in kilobytes. Default: 81920

Database connection configuration

WORDPRESS_DATABASE_HOST: Hostname for the MariaDB or MySQL server. Default: mariadb
WORDPRESS_DATABASE_PORT_NUMBER: Port used by the MariaDB or MySQL server. Default: 3306
WORDPRESS_DATABASE_NAME: Database name that WordPress for Intel will use to connect with the database. Default: bitnami_wordpress
WORDPRESS_DATABASE_USER: Database user that WordPress for Intel will use to connect with the database. Default: bn_wordpress
WORDPRESS_DATABASE_PASSWORD: Database password that WordPress for Intel will use to connect with the database. No defaults.
WORDPRESS_ENABLE_DATABASE_SSL: Whether to enable SSL for database connections. Default: no
WORDPRESS_VERIFY_DATABASE_SSL: Whether to verify the database SSL certificate when SSL is enabled for database connections. Default: yes
WORDPRESS_DATABASE_SSL_CERT_FILE: Path to the database client certificate file. No defaults
WORDPRESS_DATABASE_SSL_KEY_FILE: Path to the database client certificate key file. No defaults
WORDPRESS_DATABASE_SSL_CA_FILE: Path to the database server CA bundle file. No defaults
ALLOW_EMPTY_PASSWORD: It can be used to allow blank passwords. Default: no

Create a database for WordPress for Intel using mysql-client

MYSQL_CLIENT_FLAVOR: SQL database flavor. Valid values: mariadb or mysql. Default: mariadb
MYSQL_CLIENT_DATABASE_HOST: Hostname for the MariaDB or MySQL server. Default: mariadb
MYSQL_CLIENT_DATABASE_PORT_NUMBER: Port used by the MariaDB or MySQL 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_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 WordPress for Intel to send email using SMTP you can set the following environment variables:

WORDPRESS_SMTP_HOST: SMTP host.
WORDPRESS_SMTP_PORT: SMTP port.
WORDPRESS_SMTP_USER: SMTP account user.
WORDPRESS_SMTP_PASSWORD: SMTP account password.

PHP configuration

PHP_ENABLE_OPCACHE: Enable OPcache for PHP scripts. Default: yes
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: 512M
PHP_POST_MAX_SIZE: Maximum size for PHP POST requests. No default.
PHP_UPLOAD_MAX_FILESIZE: Maximum file size for PHP uploads. No default.

Examples

SMTP configuration using a Gmail account

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

Modify the docker-compose.yml file present in this repository:

  wordpress:
    ...
    environment:
      - WORDPRESS_DATABASE_USER=bn_wordpress
      - WORDPRESS_DATABASE_NAME=bitnami_wordpress
      - ALLOW_EMPTY_PASSWORD=yes
      - WORDPRESS_SMTP_HOST=smtp.gmail.com
      - WORDPRESS_SMTP_PORT=587
      - WORDPRESS_SMTP_USER=your_email@gmail.com
      - WORDPRESS_SMTP_PASSWORD=your_password
  ...

For manual execution:

$ docker run -d --name wordpress -p 80:8080 -p 443:8443 \
  --env WORDPRESS_DATABASE_USER=bn_wordpress \
  --env WORDPRESS_DATABASE_NAME=bitnami_wordpress \
  --env WORDPRESS_SMTP_HOST=smtp.gmail.com \
  --env WORDPRESS_SMTP_PORT=587 \
  --env WORDPRESS_SMTP_USER=your_email@gmail.com \
  --env WORDPRESS_SMTP_PASSWORD=your_password \
  --network wordpress-tier \
  --volume /path/to/wordpress-persistence:/bitnami \
  bitnami/wordpress-intel:latest

Connect WordPress for Intel container to an existing database

The Bitnami WordPress for Intel container supports connecting the WordPress for Intel application to an external database. This would be an example of using an external database for WordPress for Intel.

Modify the docker-compose.yml file present in this repository:

   wordpress:
     ...
     environment:
-      - WORDPRESS_DATABASE_HOST=mariadb
+      - WORDPRESS_DATABASE_HOST=mariadb_host
       - WORDPRESS_DATABASE_PORT_NUMBER=3306
       - WORDPRESS_DATABASE_NAME=wordpress_db
       - WORDPRESS_DATABASE_USER=wordpress_user
-      - ALLOW_EMPTY_PASSWORD=yes
+      - WORDPRESS_DATABASE_PASSWORD=wordpress_password
     ...

For manual execution:

$ docker run -d --name wordpress\
  -p 8080:8080 -p 8443:8443 \
  --network wordpress-network \
  --env WORDPRESS_DATABASE_HOST=mariadb_host \
  --env WORDPRESS_DATABASE_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/wordpress \
  bitnami/wordpress-intel:latest

In case the database already contains data from a previous WordPress for Intel installation, you need to set the variable WORDPRESS_SKIP_BOOTSTRAP to yes. Otherwise, the container would execute the installation wizard and could modify the existing data in the database. Note that, when setting WORDPRESS_SKIP_BOOTSTRAP to yes, values for environment variables such as WORDPRESS_USERNAME, WORDPRESS_PASSWORD or WORDPRESS_EMAIL will be ignored. Make sure that, in this imported database, the table prefix matches the one set in WORDPRESS_TABLE_PREFIX.

WP-CLI tool

The Bitnami WordPress for Intel container includes the command line interface wp-cli that can help you to manage and interact with your WP sites. To run this tool, please note you need use the proper system user, daemon.

This would be an example of using wp-cli to display the help menu:

Using docker-compose command:

$ docker-compose exec wordpress wp help

Using docker command:

$ docker exec wordpress wp help

Find more information about parameters available in the tool in the official documentation.

Logging

The Bitnami WordPress for Intel Docker image sends the container logs to stdout. To view the logs:

$ docker logs wordpress

Or using Docker Compose:

$ docker-compose logs wordpress

You can configure the containers logging driver 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

$ docker stop wordpress

Or using Docker Compose:

$ docker-compose stop wordpress

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.

$ docker run --rm -v /path/to/wordpress-backups:/backups --volumes-from wordpress busybox \
  cp -a /bitnami/wordpress /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:

 $ 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 WordPress for Intel container:

 $ docker run -d --name wordpress \
   ...
-  --volume /path/to/wordpress-persistence:/bitnami/wordpress \
+  --volume /path/to/wordpress-backups/latest:/bitnami/wordpress \
   bitnami/wordpress-intel:latest

Upgrade this image

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

The bitnami/wordpress-intel: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-intel:latest. However it is recommended to use tagged versions.

Step 1: Get the updated image

$ docker pull bitnami/wordpress-intel:latest

Step 2: Stop the running container

Stop the currently running container using the command

$ docker-compose stop wordpress

Step 3: Take a snapshot of the application state

Follow the steps in 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:

docker-compose rm -v wordpress

Step 5: Run the new image

Update the image tag in docker-compose.yml and re-create your container with the new image:

$ docker-compose up -d

Customize this image

The Bitnami WordPress for Intel 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 port used by NGINX for HTTP setting the environment variable NGINX_HTTP_PORT_NUMBER.
Adding custom server blocks.
Replacing the 'nginx.conf' file.
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:

FROM bitnami/wordpress-intel
## Put your customizations below
...

Modify the NGINX configuration file
Modify the ports used by NGINX
Change the user that runs the container

FROM bitnami/nginx
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

### Modify 'worker_connections' on NGINX config file to '512'
RUN sed -i -r "s#(\s+worker_connections\s+)[0-9]+;#\1512;#" /opt/bitnami/nginx/conf/nginx.conf

### Modify the ports used by NGINX by default
ENV NGINX_HTTP_PORT_NUMBER=8181 # It is also possible to change this environment variable at runtime
EXPOSE 8181 8143

### Modify the default container user
USER 1002

Based on the extended image, you can update the docker-compose.yml file present in this repository to add other features:

   wordpress:
-    image: bitnami/wordpress-intel:latest
+    build: .
     ports:
-      - '80:8080'
-      - '443:8443'
+      - '80:8181'
+      - '443:8143'
     environment:
+      - PHP_MEMORY_LIMIT=512m
     ...

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
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.

README.md Unescape Escape

WordPress for Intel packaged by Bitnami

What is WordPress for Intel?

TL;DR

Why use Intel optimized containers

Why use Bitnami Images?

How to deploy WordPress for Intel in Kubernetes?

Why use a non-root container?

Supported tags and respective Dockerfile links

Get this image

How to use this image

Run the application using Docker Compose

Using the Docker Command Line

Step 1: Create a network

Step 2: Create a volume for MariaDB persistence and create a MariaDB container

Step 3: Create volumes for WordPress for Intel persistence and launch the container

Persisting your application

Mount host directories as data volumes with Docker Compose

Mount host directories as data volumes using the Docker command line

Step 1: Create a network (if it does not exist)

Step 2. Create a MariaDB container with host volume

Step 3. Create the WordPress for Intel container with host volumes

Configuration

Environment variables

User and Site configuration

Multisite configuration

Database connection configuration

Create a database for WordPress for Intel using mysql-client

SMTP Configuration

PHP configuration

Examples

SMTP configuration using a Gmail account

Connect WordPress for Intel container to an existing database

WP-CLI tool

Logging

Maintenance

Backing up your container

Step 1: Stop the currently running container

Step 2: Run the backup command

Restoring a backup

Upgrade this image

Step 1: Get the updated image

Step 2: Stop the running container

Step 3: Take a snapshot of the application state

Step 4: Remove the currently running container

Step 5: Run the new image

Customize this image

Extend this image

Contributing

Issues

License

README.md

Supported tags and respective `Dockerfile` links