kevinveenbirkenbachandClaude Opus 4.8
de95b5f240
The playwright beforeEach required KEYCLOAK_BASE_URL, OIDC_ISSUER_URL and
the super-admin credentials unconditionally, but playwright.env.j2 sets
SUPER_ADMIN_* to "" when SSO is off, so non-SSO variants failed with
"SUPER_ADMIN_USERNAME must be set" at spec line 508. Wrap those checks
in isServiceEnabled("sso") (the same SSO_SERVICE_ENABLED flag the
template keys off), matching the dashboard role. The SSO variant still
runs them; both swarm and compose non-SSO variants were affected.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
WordPress
Description
WordPress is a versatile and widely used content management system (CMS) that powers millions of websites, from blogs and portfolios to e-commerce and corporate sites. This deployment provides a containerized WordPress instance optimized for multisite operation, advanced media management, and extensive plugin support, allowing you to fully leverage the rich features of the WordPress software.
Overview
WordPress offers an extensive array of features that make it a robust platform for building and managing digital content:
-
User-Friendly Interface: Enjoy a modern, intuitive dashboard for effortless content creation, editing, and management.
-
Customizable Themes and Plugins: Extend your site's functionality with thousands of themes and plugins, enabling you to tailor your website's look, feel, and capabilities to your exact needs.
-
Multisite Management: Easily create and maintain multiple sites with a single WordPress installation, ideal for networks of blogs, corporate intranets, or educational institutions.
-
Responsive Design: Ensure that your website looks great on all devices with mobile-friendly themes and layouts.
-
Advanced SEO Tools: Optimize your site's visibility in search engines using built-in support for SEO best practices and a rich ecosystem of SEO plugins.
-
Robust Media Management: Manage your images, videos, and other media with an integrated media library, including options for enhanced upload limits and dynamic content delivery.
-
Extensive Community and Ecosystem: Benefit from a massive community with frequent updates, security patches, and a wide range of third-party tools that continuously enhance the platform.
This automated Docker Compose deployment streamlines the process by building a custom WordPress image (which includes tools like msmtp for email delivery) and configuring the necessary PHP settings, ensuring that your WordPress site is secure, scalable, and always up to date.
Features
- Automated provisioning: Configured by Ansible without manual steps.
Purpose
The goal of this deployment is to provide a production-ready, scalable WordPress instance with multisite capabilities and enhanced performance. By automating the custom image build and configuration processes via Docker Compose and Ansible, it minimizes manual intervention, reduces errors, and allows you to concentrate on building great content.
Multisite (requirement 005)
WordPress Multisite is opt-in. Set services.wordpress.multisite.enabled: true in the inventory to convert the deployed instance into a sub-domain Multisite network. Every entry in domains.canonical becomes a site in the network; the first entry is the network primary, subsequent entries are child sites.
RBAC under Multisite uses the hierarchical Keycloak group path:
- Per-site role:
/roles/web-app-wordpress/<canonical-domain>/<role> - Network-wide super-admin:
/roles/web-app-wordpress/network-administrator
Operator-facing instructions for assigning these groups live in Administration RBAC. The design contract is in RBAC design.
Addons
Plugins and the OIDC→RBAC mu-plugin are declared in
meta/addons/ under the unified addon contract
(requirement 026). The OIDC and WP-Discourse runtime config lives in each addon's config: block.
| Addon | Mechanism | Default state | Bridges |
|---|---|---|---|
daggerhart-openid-connect-generic |
plugin |
enabled with the sso service |
sso → web-app-keycloak |
wp-discourse |
plugin |
enabled with the discourse service |
discourse → web-app-discourse |
activitypub |
plugin |
always enabled (Fediverse federation) | none |
infinito-oidc-rbac-mapper |
mu_plugin |
required (always installed, vendored) |
sso → web-app-keycloak |
The OIDC login + RBAC paths are covered by test-admin-oidc-login.js /
test-rbac-roles.js, the Discourse round-trip by test-discourse-roundtrip.js.
Playwright service dependencies
The Playwright suite in files/playwright/playwright.spec.js gates its scenarios on the following shared services (requirement 006). Scenarios that depend on a service report as skipped when the corresponding <SERVICE>_SERVICE_ENABLED=false in the staged .env:
oidc: baseline admin OIDC round-trip plus the three RBAC scenarios (subscriber/editor/administrator).ldap: the three RBAC scenarios additionally depend on LDAP group sync; disabling LDAP skips them alongside OIDC.discourse: the WP->Discourse post round-trip scenario (requirement 007). Disabling Discourse skips it; front-page reachability and CSP baselines stay active.
The front-page CSP + canonical-domain baseline is ungated and always runs.
Further Resources
- WordPress Official Website
- WordPress Multisite Documentation
- WordPress Plugin Repository
- WP Discourse Plugin
Credits
Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).