full stack nginx WordPress for everyone with docker compose

If You want to build a website with WordPress at short time;

Full stack Nginx WordPress:

Plus, manage docker containers with Portainer.

Supported CPU architectures:

Supported Linux Package Manage Systems:

Supported Linux Operation Systems:

Note: Fedora 37, 39 and alpine linux x86-64 compatible, could not try sles IBM Z s390x, rhel IBM Z s390x and raspberrypi.

After installing the repository, a system reboot is required on Red Hat OS, Arch Linux.

With this project you can quickly run the following:

• WordPress (php-fpm)
• webserver (nginx)
• certbot (letsencrypt)
• phpMyAdmin
• Mariadb Mysql
• redis
• varnish
• backup

For certbot (letsencrypt) certificate:

• Set DNS configuration of your domain name

IPv4/IPv6 Firewall

Create rules to open ports to the internet, or to a specific IPv4 address or range.

• http: 80
• https: 443
• portainer: 9001
• phpmyadmin: 9090

Note

To optimize upload images, look at the damalis repository

Required Ram

require up to 2 GB of RAM for Docker and Docker Compose.

Contents:

• Auto Configuration and Installation
• Manual Configuration and Installation
  • Requirements
  • Configuration
  • Installation
• Portainer Installation
• Usage
  • Website
  • Webserver
  • Redis Plugin
  • Varnish Plugin
  • phpMyAdmin
  • backup

Automatic

Exec install shell script for auto installation and configuration

download with

git clone https://github.com/damalis/full-stack-nginx-wordpress-for-everyone-with-docker-compose.git

Open a terminal and cd to the folder in which docker-compose.yml is saved and run:

cd full-stack-nginx-wordpress-for-everyone-with-docker-compose
chmod +x install.sh
LC_ALL=C.UTF-8 ./install.sh # LC_ALL=C.UTF-8 if not os language english

Manual

Requirements

Make sure you have the latest versions of Docker and Docker Compose installed on your machine and require up to 2 GB of RAM.

• How install docker
• How install docker compose

Clone this repository or copy the files from this repository into a new folder.

Make sure to add your user to the docker group.

Configuration

download with

git clone https://github.com/damalis/full-stack-nginx-wordpress-for-everyone-with-docker-compose.git

Open a terminal and cd to the folder in which docker-compose.yml is saved and run:

cd full-stack-nginx-wordpress-for-everyone-with-docker-compose

Copy the example environment into .env

cp env.example .env

Edit the .env file to change values of

|LOCAL_TIMEZONE|DOMAIN_NAME|DIRECTORY_PATH|LETSENCRYPT_EMAIL| |WORDPRESS_DB_USER|WORDPRESS_DB_PASSWORD|WORDPRESS_DB_NAME|WORDPRESS_TABLE_PREFIX|MYSQL_ROOT_PASSWORD|DATABASE_IMAGE_NAME| |DATABASE_CONT_NAME|DATABASE_PACKAGE_MANAGER|DATABASE_ADMIN_COMMANDLINE|PMA_CONTROLUSER|PMA_CONTROLPASS| |PMA_HTPASSWD_USERNAME|PMA_HTPASSWD_PASSWORD|VARNISH_VERSION|VARNISH_VERSION|SSL_SNIPPET|

Variable	Value
LOCAL_TIMEZONE	to see local timezones
DIRECTORY_PATH	pwd at command line
WORDPRESS_TABLE_PREFIX	wp_ or custom value
DATABASE_IMAGE_NAME	mariadb or mysql
DATABASE_CONT_NAME	mariadb, mysql or custom name
DATABASE_PACKAGE_MANAGER	mariadb	apt-get update && apt-get install -y gettext-base
mysql	microdnf update -y && microdnf install -y gettext
DATABASE_ADMIN_COMMANDLINE	mariadb	mariadb-admin
mysql	mysqladmin
VARNISH_VERSION	centos version 9+ and fedora	latest
the others	stable
SSL_SNIPPET	localhost	echo 'Generated Self-signed SSL Certificate at localhost'
remotehost	certbot certonly --webroot --webroot-path /tmp/acme-challenge --rsa-key-size 4096 --non-interactive --agree-tos --no-eff-email --force-renewal --email ${LETSENCRYPT_EMAIL} -d ${DOMAIN_NAME} -d www.${DOMAIN_NAME} -d mail.${DOMAIN_NAME}

Installation

Firstly: will create external volume

docker volume create --driver local --opt type=none --opt device=${PWD}/certbot --opt o=bind certbot-etc

Localhost ssl: Generate Self-signed SSL Certificate with guide mkcert repository.

docker compose up -d

then reloading for webserver ssl configuration

docker container restart webserver

The containers are now built and running. You should be able to access the WordPress installation with the configured IP in the browser address. https://DOMAIN_NAME.

For convenience you may add a new entry into your hosts file.

Portainer

docker compose -f portainer-docker-compose.yml -p portainer up -d 

manage docker with Portainer is the definitive container management tool for Docker, Docker Swarm with it's highly intuitive GUI and API.

You can also visit https://DOMAIN_NAME:9001 to access portainer after starting the containers.

Usage

You could manage docker containers without command line with portainer.

Here’s a quick reference of commonly used Docker Compose commands

docker ps -a # Lists all containers managed by the compose file

docker compose start # Starts previously stopped containers

docker compose stop # Stops all running containers

docker compose down # Stops and removes containers, networks, etc.

docker compose down -v # Add --volumes to remove volumes explicitly

docker rm -f $(docker ps -a -q) # Removes portainer and the other containers

docker volume rm $(docker volume ls -q) # Removes all volumes

docker network prune # Remove all unused networks

docker system prune # Removes unused data (containers, networks, images, and optionally volumes)

docker system prune -a # Removes all unused images, not just dangling ones

docker rmi $(docker image ls -q) # Removes portainer and the other images

docker container logs container_name_or_id # Shows logs from all services

Project from existing source

Copy all files into a new directory:

docker compose up -d # Starts services in detached mode (in the background)

Docker run reference

https://docs.docker.com/reference/cli/docker/compose/

Website

You should see the "Wordpress installation" page in your browser. If not, please check if your PHP installation satisfies WordPress's requirements.

https://DOMAIN_NAME

add or remove code in the ./php-fpm/php/conf.d/security.ini file for custom php.ini configurations

https://www.php.net/manual/en/configuration.file.php

You should make changes custom host configurations ./php-fpm/php-fpm.d/z-www.conf then must restart service, FPM uses php.ini syntax for its configuration file - php-fpm.conf, and pool configuration files.

https://www.php.net/manual/en/install.fpm.configuration.php

docker container restart wordpress

add and/or remove wordpress site folders and files with any ftp client program in ./wordpress folder.
You can also visit https://DOMAIN_NAME to access website after starting the containers.

Webserver

add or remove code in the ./webserver/templates/nginx.conf.template file for custom nginx configurations

https://docs.nginx.com/nginx/admin-guide/basic-functionality/managing-configuration-files/

Redis Plugin

add and active Redis Cache plugin and

must add below code in wp-config.php file.

define('WP_REDIS_HOST', 'redis');
define('WP_CACHE_KEY_SALT', 'wp-docker-7f1a7682-9aec-4d4b-9a10-46bbadec41ba');
define('WP_REDIS_PREFIX', $_SERVER['HTTP_HOST']);
define('WP_REDIS_CONFIG', [
	'prefix' => getenv('WP_REDIS_PREFIX') ?: null,
    'timeout' => 0.5,
    'read_timeout' => 0.5,
    'async_flush' => true,
    'compression' => 'zstd',
    'serializer' => 'igbinary',
    'split_alloptions' => true,
    'debug' => false,
    'save_commands' => false,
]);

Varnish Plugin

add and active Proxy Cache Purge plugin.

Proxy Cahe -> Settings -> Configure Custom IP -> Set Custom IP: varnish

Configuration file: ./varnish/default.vcl

Go to the WordPress dashboard
Click on Plugins
Click on Add New
Search for the Redis Cache / the Proxy Cache Purge plugin
Click on Install Now and confirm
Finally, activate the plugin

add this code to connect always with ssl in wp-config.php file.

define('FORCE_SSL_LOGIN', true);
define('FORCE_SSL_ADMIN', true);

after every change in the wordpress and the varnish configuration or if You get error "502 Bad Gateway":

docker container restart varnish

phpMyAdmin

You can add your own custom config.inc.php settings (such as Configuration Storage setup) by creating a file named config.user.inc.php with the various user defined settings in it, and then linking it into the container using:

./phpmyadmin/config.user.inc.php

You can also visit https://DOMAIN_NAME:9090 to access phpMyAdmin after starting the containers.

The first authorize screen(htpasswd;username or password) and phpmyadmin login screen the username and the password is the same as supplied in the .env file.

backup

This will back up the all files and folders in database/dump sql and html volumes, once per day, and write it to ./backups with a filename like backup-2023-01-01T10-18-00.tar.gz

can run on a custom cron schedule

BACKUP_CRON_EXPRESSION: '20 01 * * *' the UTC timezone.