All projects

Containerised WordPress Platform

Multi-site WordPress and MariaDB on Synology under Docker, with Redis, reverse proxy and a repeatable per-site layout.

Diagram of the containerised WordPress platform: NGINX reverse proxy at the edge, Docker on Synology DSM, shared Adminer and DNS, and four per-site containers for WordPress, MariaDB, Redis and file access.

Context: Personal infrastructure

The brief

Run multiple WordPress sites on a self-hosted platform with a deployment pattern that can be repeated for each new site.

What I built

Docker on Synology DSM runs WordPress and MariaDB per site, with Redis object caching. A shared Adminer instance supports database administration, while an NGINX reverse proxy handles incoming HTTPS traffic and TLS termination.

How it is organised

Standardised container names and volume layouts make the relationship between each site, its database and its persistent files explicit. New sites follow the same deployment structure.

The operational result

The platform provides a repeatable per-site layout while sharing the host and supporting services. Those shared dependencies remain part of the operating design; separate containers do not remove the dependency on the Synology host.

Related work

How I administer this site through an AI connection · The measured portfolio theme trial

See the self-hosted service inventory · Explore the stack and its public edge

Explore connected work