This repository will build a container image for running Wordpress. A Content Management System.

• Nfrastack

• About
• Maintainer
• Table of Contents
• Prerequisites and Assumptions
• Installation
  • Build from Source
  • Prebuilt Images
    • Multi-Architecture Support
• Configuration
  • Quick Start
  • Persistent Storage
  • Environment Variables
    • Base Images used
    • Core Configuration
  • Users and Groups
  • Networking
• Maintenance
  • Shell Access
  • Local Development / Changing Site Name & Ports
  • Command Line
• Support & Maintenance
• License
• References

Feature limited builds of the image are available on the Github Container Registry and Docker Hub.

To unlock advanced features, one must provide a code to be able to change specific environment variables from defaults. Support the development to gain access to a code.

To get access to the image use your container orchestrator to pull from the following locations:

ghcr.io/nfrastack/container-wordpress:(image_tag)
docker.io/nfrastack/wordpress:(image_tag)

Image tag syntax is:

<image>:<optional tag>-<optional phpversion>-<optional distro>-<optional distro_variant>

Example:

docker.io/nfrastack/container-wordpress:latest or

ghcr.io/nfrastack/container-wordpress:1.0-php84-alpine

• latest will be the most recent commit

• An optional tag may exist that matches the CHANGELOG - These are the safest

Have a look at the container registries and see what tags are available.

Images are built for amd64 by default, with optional support for arm64 and other architectures.

• The quickest way to get started is using docker-compose. See the examples folder for a working compose.yml that can be modified for your use.

• Map persistent storage for access to configuration and data files for backup.

• Set various environment variables to understand the capabilities of this image.

The following directories/files should be mapped for persistent storage in order to utilize the container effectively.

This image relies on a customized base image in order to work. Be sure to view the following repositories to understand all the customizable options:

Below is the complete list of available options that can be used to customize your installation.

• Variables showing an 'x' under the Advanced column can only be set if the containers advanced functionality is enabled.

For debugging and maintenance, bash and sh are available in the container.

Wordpress assets are delivered by means of the initial Site URL, and if you wish to develop locally or on a different port you will experience strange results. If you are performing local development then you would want to setup your environment variables as such:

• ENABLE_HTTPS_REVERSE_PROXY=FALSE
• SITE_URL=localhost
• SITE_PORT=8000 (or whatever port you are exposing)

When you are ready to deploy to a production URL - you would change it as such:

• ENABLE_HTTPS_REVERSE_PROXY=TRUE
• SITE_URL=www.domain.com

The system will rotate the URLs in the wordpress configuration files and database automatically upon restart of the container.

If you wish to use the included wp-cli tool to perform maintenance use it as such:

cd /www/wordpress
wp-cli <argument>

• For community help, tips, and community discussions, visit the Discussions board.
• For personalized support or a support agreement, see Nfrastack Support.
• To report bugs, submit a Bug Report. Usage questions will be closed as not-a-bug.
• Feature requests are welcome, but not guaranteed. For prioritized development, consider a support agreement.
• Updates are best-effort, with priority given to active production use and support agreements.

• https://wordpress.net/
• https://github.com/wordpress-helpdesk/wordpress/wiki/Installation-Guide

This project is licensed under the MIT License - see the LICENSE file for details.