5.2.1-ol-7-r10 release
This commit is contained in:
Bitnami Bot
parent
57f02491c2
commit
4e1b2f77bc
|
|
@ -1,4 +1,4 @@
|
|||
FROM bitnami/oraclelinux-extras:7-r352
|
||||
FROM bitnami/oraclelinux-extras:7-r353
|
||||
LABEL maintainer "Bitnami <containers@bitnami.com>"
|
||||
|
||||
# Install required system packages and dependencies
|
||||
|
|
@ -14,7 +14,7 @@ RUN ln -sf /dev/stderr /opt/bitnami/nginx/logs/error.log
|
|||
COPY rootfs /
|
||||
ENV ALLOW_EMPTY_PASSWORD="no" \
|
||||
BITNAMI_APP_NAME="wordpress-nginx" \
|
||||
BITNAMI_IMAGE_VERSION="5.2.1-ol-7-r9" \
|
||||
BITNAMI_IMAGE_VERSION="5.2.1-ol-7-r10" \
|
||||
MARIADB_HOST="mariadb" \
|
||||
MARIADB_PORT_NUMBER="3306" \
|
||||
MARIADB_ROOT_PASSWORD="" \
|
||||
|
|
|
|||
|
|
@ -46,8 +46,8 @@ $ kubectl apply -f test.yaml
|
|||
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/).
|
||||
|
||||
|
||||
* [`5-ol-7`, `5.2.1-ol-7-r9` (5/ol-7/Dockerfile)](https://github.com/bitnami/bitnami-docker-wordpress-nginx/blob/5.2.1-ol-7-r9/5/ol-7/Dockerfile)
|
||||
* [`5-debian-9`, `5.2.1-debian-9-r8`, `5`, `5.2.1`, `5.2.1-r8`, `latest` (5/debian-9/Dockerfile)](https://github.com/bitnami/bitnami-docker-wordpress-nginx/blob/5.2.1-debian-9-r8/5/debian-9/Dockerfile)
|
||||
* [`5-ol-7`, `5.2.1-ol-7-r10` (5/ol-7/Dockerfile)](https://github.com/bitnami/bitnami-docker-wordpress-nginx/blob/5.2.1-ol-7-r10/5/ol-7/Dockerfile)
|
||||
* [`5-debian-9`, `5.2.1-debian-9-r9`, `5`, `5.2.1`, `5.2.1-r9`, `latest` (5/debian-9/Dockerfile)](https://github.com/bitnami/bitnami-docker-wordpress-nginx/blob/5.2.1-debian-9-r9/5/debian-9/Dockerfile)
|
||||
* [`5-rhel-7`, `5.1.1-rhel-7-r40` (5/rhel-7/Dockerfile)](https://github.com/bitnami/bitnami-docker-wordpress-nginx/blob/5.1.1-rhel-7-r40/5/rhel-7/Dockerfile)
|
||||
|
||||
Subscribe to project updates by watching the [bitnami/wordpress-nginx GitHub repo](https://github.com/bitnami/bitnami-docker-wordpress-nginx).
|
||||
|
|
@ -329,12 +329,93 @@ $ docker run -d --name wordpress -p 80:80 -p 443:443 \
|
|||
bitnami/wordpress-nginx:latest
|
||||
```
|
||||
|
||||
# Customize this image
|
||||
|
||||
The Bitnami WordPress with NGINX 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/wordpress-nginx
|
||||
## 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/wordpress-nginx
|
||||
LABEL maintainer "Bitnami <containers@bitnami.com>"
|
||||
|
||||
## Install 'vim'
|
||||
RUN install_packages vim
|
||||
|
||||
## 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 use a Docker Compose file like the one below to add other features:
|
||||
|
||||
```yaml
|
||||
version: '2'
|
||||
services:
|
||||
mariadb:
|
||||
image: 'bitnami/mariadb:10.3'
|
||||
volumes:
|
||||
- 'mariadb_data:/bitnami'
|
||||
environment:
|
||||
- MARIADB_USER=bn_wordpress
|
||||
- MARIADB_DATABASE=bitnami_wordpress
|
||||
- ALLOW_EMPTY_PASSWORD=yes
|
||||
wordpress:
|
||||
build: .
|
||||
ports:
|
||||
- '80:8181'
|
||||
- '443:8143'
|
||||
volumes:
|
||||
- 'wordpress_data:/bitnami'
|
||||
- './wordpress-server-block.conf:/opt/bitnami/nginx/conf/server_blocks/wordpress-server-block.conf'
|
||||
depends_on:
|
||||
- mariadb
|
||||
environment:
|
||||
- MARIADB_HOST=mariadb
|
||||
- MARIADB_PORT_NUMBER=3306
|
||||
- WORDPRESS_DATABASE_USER=bn_wordpress
|
||||
- WORDPRESS_DATABASE_NAME=bitnami_wordpress
|
||||
- ALLOW_EMPTY_PASSWORD=yes
|
||||
volumes:
|
||||
mariadb_data:
|
||||
driver: local
|
||||
wordpress_data:
|
||||
driver: local
|
||||
```
|
||||
|
||||
# Notable Changes
|
||||
|
||||
## 5.2.1-debian-9-r8 and 5.2.1-ol-7-r8
|
||||
|
||||
- This image has been adapted so it's easier to customize. See the [Customize this image](#customize-this-image) section for more information.
|
||||
- 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`. Find an example at [Using custom SSL certificates](#using-custom-ssl-certificates).
|
||||
- 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
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue