WordPress Hosting
This module describes how self-managed WordPress + WooCommerce event sites are built and run on the cluster. It is the platform pattern — reusable for any event site — not the setup of any one site.
It is distinct from two neighbouring topics:
-
WordPress Event Plugin — the public-facing event page content and its integration with the EMS back end.
-
WordPress Payment Integration — how WooCommerce checkout talks to the EMS API.
This module is about the hosting substrate: the image, storage, configuration and the plugin/theme catalogue.
What belongs here
| Page | Covers |
|---|---|
The design of a single site: read-only Bedrock image, external database, persistent uploads, ingress/TLS, bootstrap, WP-Cron, backups, and upgrade/cutover flow. |
|
The generic model for getting plugins and themes into an immutable image — public (Composer/WPackagist) vs private/commercial (baked artefacts) — licensing, and the read-only-filesystem writable-path rules every plugin is measured against. |
|
Plugin catalogue |
One page per plugin/theme in current use, giving its source, install method, and any special configuration (PVCs, writable dirs, env, licensing, caveats). |