This project automates the creation of multiple independent LEMP stacks in Docker, as well as automating the creation of Wordpress containers. Each LEMP Stack creates its own Virtual host local development domain any Wordpress container created underneath will be added as a subdomain within a LEMP stack's virtual host domain and SSL Certificate.

CLI Utility Tool script that launches a menu system with options to manage multiple Docker LEMP stacks and their respective WordPress containers. Terminal prompts to choose tasks within each. Creating LEMP stacks, Creating Wordpress containers, and management of each.

Open the project directory in a terminal and run

sh start.sh 

This will attempt to install any package managers or packages for your specifc operating system that will automate the process before showing you the menu system.

# MULTISTACK OPTIONS # __________________ # # > 1. Create New LEMP Stack # > 2. Manage domain-one # > 3. Manage domain-two # > 4. Help # > 5. Quit # # >>> What would you like to do? # >>> 

# DOMAIN-ONE OPTIONS # _______________________ # # > 1. Create New WordPress Container # > 2. Start domain-one # > 3. Restart domain-one # > 4. Stop domain-one # > 5. Open https://domain-one.test in Browser # > 6. Open https://phpmyadmin.domain-one.test in Browser # > 7. Database: Backup Dump # > 8. Database: Recover Tables # > 9. Remove domain-one # > 10. Help # > 11. Back to Main Menu # > 12. Quit # # >>> Select an option for domain-one: # >>> 

⚠️ POSIX-COMPATIBILITY NOTE

This project was only tested on macOS’s zsh/bash however written to be POSIX-compatible. The project contains code blocks where homebrew is used as the package manager for package download/install/and checks as well as including conditionals to check for os specific, e.g. Chocolatey or Scoop on Windows, however the efficacy of these code blocks were not tested. Submit pull requests if you fix anything for other operating systems.

• Terminal of choice – e.g. iTerm2 (macOS) or your preferred terminal emulator.
• Package manager – Homebrew (macOS/Linux), Chocolatey or Scoop (Windows) to install other tools
• Docker Desktop / Docker Engine – Docker to run containers
• mkcert – mkcert for generating local SSL certificates (https://github.com/FiloSottile/mkcert)

Each LEMP stack runs in Docker and includes:

• PHP Empty 'html' directory to run any php code you want.
• Nginx (unique server domain and configuration)
• MySQL or MariaDB database served on the network allowing Wordpress containers to share the database for centralized files
• phpMyAdmin Management of all wordpress database tables created underneath this LEMP stack through root user. Each Wordpress connects via unique credentials.
• SSL certificates for domain and all subdomains

Each WordPress container runs in Docker and is connected to a specific LEMP stack's database on the same network.

• Has its own subdomain and inherits SSL certificate from its LEMP stack's domain.
• Each Wordpress container shares the parent LEMP stack's database but connects to it's unique database via its own user and pass provided by your input during the terminal

• Runs traefik to route browsers to each LEMP Stack virtual host domain and subdomains.
• Building LEMP Stacks creates a new virtual host config file in traefik/dynamic. e.g. https://domain-one.test, https://phpmyadmin.domain-one.test
• Building Wordpress Containers creates a new virtual host subdomain for parent LEMP's domain config file. e.g. https://subdomain-one.domain-one.test

• Creates new virutal host domains, Nginx, MySQL, PHP, and phpMyAdmin
• Unique PHP root directory and independant PHP version for files hosted from the $STACK_NAME/html directory.
• LEMP stack's database container contains all databases unique to the LEMP stack and databases created for Wordpress containers under this LEMP STACK.
• LEMP stack's PHP container version DOES NOT affect LEMP STACK phpMyAdmin NOR WordPress container's PHP version.
• LEMP stack phpMyAdmin routed under LEMP STACK's main domain, (ie https://phpmyadmin.domain-one.test)
• LEMP STACK phpMyAdmin container runs its on PHP version inside its own container.
• LEMP STACK phpMyAdmin container connects to the LEMP's MYSQL container hosting databases unique to the LEMP stack.

• Creates a new subdomain under LEMP STACK's main domain, and unique traefik config file for this subdomain
• Connects to the LEMP Stack docker network LEMP STACK MYSQL container to create database during set up of this WordPress container.
• Wordpress images contain its own PHP version. (ie wordpress:latest = PHP likely > 8.x.x)
• DOES NOT use the LEMP STACK PHP container.
• Runs independently.

• Forget MAMP/LAMP thats for GRAMPS
• Automated LEMP stacks to quickly spin up any version of php, mysql, and wordpress and launch the browser to display phpmyadmin and main LEMP stack domain on completion of script.
• Isolated Docker networks to serve various images for different projects
• Automated Virtual Host and Traefik configuration:
  • Creates locally signed certificates for virtual host domains and subdomains automatically as well as making changes to your hosts file for you.
• Automated database backups with customizable menu options per LEMP stack

• Fully modular — add or remove LEMP stacks without impacting others
• Centralized Traefik reverse proxy for routing and SSL management
• Organized, automated backup strategy (daily + monthly retention)
• Scalable to host multiple WordPress sites per LEMP stack
• Compatible with Docker Compose for orchestration

graph TD subgraph Traefik Reverse Proxy T1(Traefik) end subgraph domain-two.test N1(Nginx) DB1[(MySQL/MariaDB)] PMA1(phpMyAdmin) WP1A(WordPress Site C subdomain-three.domain-two.test) WP1B(WordPress Site D subdomain-four.domain-two.test) end subgraph domain-one.test N2(Nginx) DB2[(MySQL/MariaDB)] PMA2(phpMyAdmin) WP2A(WordPress Site A subdomain-one.domain-one.test) WP2B(WordPress Site B subdomain-two.domain-one.test) end T1 --> N1 T1 --> N2 N1 --> WP1A N1 --> WP1B N1 --> PMA1 WP1A --- DB1 WP1B --- DB1 PMA1 --- DB1 N2 --> WP2A N2 --> WP2B N2 --> PMA2 WP2A --- DB2 WP2B --- DB2 PMA2 --- DB2 

All automation is implemented in portable POSIX shell (no Bash-only features) and organized into reusable functions.

View the directory layout below to see where the CLI tool places each *.crt & *.key files:

• /traefik/certs/*.test.crt
• /traefik/certs/*.test.key

https://domain-one.test └─ https://suddomain-one.domain-one.test └─ https://suddomain-two.domain-one.test https://domain-two.test └─ https://suddomain-three.domain-two.test └─ https://suddomain-four.domain-two.test 

lxv-multistack-lemp ├── _env-setup.sh ├── functions ├── scripts ├── stacks │ ├── domain-one (Docker Container) │ │ └── containers │ │ ├── suddomain-one (Docker Container) │	│	│	├── docker-compose.yml │	│	│	├── Dockerfile │ │ │ └─── html │ │ └── subdomain-two (Docker Container) │	│	├── docker-compose.yml │	│	├── Dockerfile │ │ └── html │ └── domain-two (Docker Container) │	└─── containers │ ├── subdomain-three (Docker Container) │	│	├── docker-compose.yml │	│	├── Dockerfile │ │ └─── html │ └── subdomain-four (Docker Container) │	├── docker-compose.yml │	├── Dockerfile │ └── html ├── start.sh ├── templates └── traefik ├── certs │ ├── domain-one.test.crt │ ├── domain-one.test.key │ ├── domain-two.test.crt │ └── domain-two.test.key ├── docker-compose.override.yml ├── docker-compose.yml ├── dynamic │ ├── certs.yml │ ├── lemp-domain-one.yml │ └── lemp-domain-two.yml └── traefik.yml 

• In the docker-compose.yml file we use variables to name containers and paths so how you name them through the menu wizard will effect how your docker compose stacks will work.
• For the following example lets say you named a LEMP stack/domain 'domain-one' e.g. LEMP_SERVER_DOMAIN_NAME="domain-one" and LEMP_SERVER_DOMAIN_TLD="test"
• The docker-compose.yml will source stacks/domain-one/.env file variables effectively naming your containers as such.
• This will also create a dockernetwork: domain_one_lemp_network that all services and wordpress containers added later will connect to. So all Wordpress containers under a LEMP stack can share one unified LEMP Stack database.

• image: phpmyadmin:latest latest is fine
• vhost: https://phpmyadmin.domain-one.test

• image: php:8.x.x-fpm-bullseye or newest version 'fpm' should be chosen
• vhost: https://domain-one.test <- empty php playground

• image: nginx:latest latest is fine

• This container will be named which ever database image you chose in the 'Create new LEMP stack' menu option -> Example: mysql:latest

• image: debian:bookworm-slim
• Currently only handles our backup scripts and cron backups
• Debian bookworm-slim can provide you with a reliable foundation plus the exact GNU utilities (find, stat, date, cron, gzip, mysql-client) that make your backup and cleanup scripts work consistently. It also opens doors for compression, encryption, offsite syncing, and observability — all directly within your backup container.

• For the following example lets say you named a LEMP stack/domain 'domain-one' and a Wordpress container/subdomain 'subdomain-one' e.g. WORDPRESS_SERVICE_CONTAINER_NAME="subdomain-one"

• image: wordpress:latest
• vhost: https://subdomain-one.domain-one.test