How rdiezsj/multisite-with-proxy-and-ssl-docker works
Project type and purpose
• This is a Docker-Compose based multi-site hosting stack.
• Purpose: centrally host multiple web applications (WordPress, DokuWiki) behind an Nginx reverse-proxy with automated Let’s Encrypt SSL.
File structure
• Top-level files:
• .env.example / .env – environment variables (domains, mail, DB creds)
• docker-compose.yml – orchestrates all containers
• vhost/ – per-domain custom Nginx server blocks
• client_max_upload_size.conf, uploads.ini – upload limits for Nginx & PHP
• uploads.ini – PHP upload limits
• vhost/test1.fake.com, vhost/test2.foo.com – optional custom rewrites
• No “src” code here—this is purely infrastructure.
• Volumes & networks are declared in docker-compose.yml.
Extract architecture hints from README
• Two sites: test1.fake.com (WordPress+MySQL), test2.foo.com (DokuWiki).
• Shared Nginx proxy + acme-companion for SSL certs.
• Uses one external Docker network (multisite-net) and one internal WordPress-MySQL network (mysqldb1).
Main components
a. External/Infrastructure
• DNS provider resolving test1.fake.com and test2.foo.com to host IP.
• Public ports 80 and 443 on the Docker host.
b. Docker Host (virtual or physical server)
• Docker Engine & Docker Compose
• External network: multisite-net
c. Containers
1. nginx-proxy
• Image: jwilder/nginx-proxy
• Listens on 80/443, mounts Docker socket to auto-generate vhosts.
• Loads per-domain config from /etc/nginx/vhost.d.
2. acme-companion
• Image: nginxproxy/acme-companion
• Hooks into nginx-proxy, uses Let’s Encrypt to obtain SSL certificates.
3. WordPress site (wordpress1)
• PHP-Apache container with VIRTUAL_HOST & LETSENCRYPT_HOST env vars.
• Connects to MySQL over internal mysqldb1 network.
• Mounts uploads.ini, WP content volume.
4. MySQL (mysqldb1)
• mysql:latest, private internal network.
• Volume for database persistence.
5. DokuWiki (dokuwiki)
• linuxserver/dokuwiki, mounts /config volume, attaches to multisite-net.
d. Volumes
• certs, html, dhparam, acme, mysqldb1, wordpress1, dokuwiki1 for persistence.
Relationships & data flows
• DNS → Host Public IP → Ports 80/443 → nginx-proxy
• nginx-proxy → routes HTTP(S) traffic to:
• wordpress1 (via multisite-net)
• dokuwiki (via multisite-net)
• wordpress1 ↔ mysqldb1 (over internal network mysqldb1)
• acme-companion ↔ nginx-proxy & Docker socket (for certificate generation)
• Volumes attached to each container for persistence.
Architectural patterns & principles
• Reverse-proxy pattern for multi-tenancy.
• Network segmentation: internal network for DB security.
• 12-factor app style: config via env vars, stateless containers, separate storage volumes.
• Automated certificate provisioning.