How pixel-guru/wordpress-multi-instance-with-mysql-replication works
A Docker Compose stack for hosting multiple isolated WordPress sites with dedicated MySQL databases and replication. The documented user path is HTTP traffic through Traefik to WordPress, which uses its local MySQL database; that database replicates to a MySQL replica. Volumes preserve site files and database data. The only implementation file is the Compose YAML; relationships below are based on README documentation, not inspected configuration excerpts.
Main entry points: muti_wordpress_em_docker.yaml WordPress instance
Components 9
Ingress and routing
- Traefik
muti_wordpress_em_docker.yaml - Traefik bridge
muti_wordpress_em_docker.yaml
WordPress site
- WordPress instance
muti_wordpress_em_docker.yaml - Site network
muti_wordpress_em_docker.yaml - WordPress files
muti_wordpress_em_docker.yaml
Database and persistence
- Site MySQL
muti_wordpress_em_docker.yaml - MySQL replica
muti_wordpress_em_docker.yaml - MySQL data
muti_wordpress_em_docker.yaml
Other components
- Site visitor
Connections 11
- Site visitor → Traefik: sends requests
README.md - Traefik → WordPress instance: routes requests
README.md - WordPress instance → Site MySQL: uses database
README.md - Site MySQL → MySQL replica: replicates data
README.md - WordPress instance → Site network: communicates on
README.md - Site MySQL → Site network: communicates on
README.md - WordPress instance → Traefik bridge: connects through
README.md - Site MySQL → Traefik bridge: connects through
README.md - MySQL replica → Traefik bridge: replicates through
README.md - WordPress instance → WordPress files: persists site files
README.md - Site MySQL → MySQL data: persists database
README.md