WordPress
otsumami.wordpress
A Docker Compose file for WordPress alone, generated from the catalog and checked by the safety inspector. No account needed.
Content management system for sites, blogs and stores, extended through themes and a very large plugin ecosystem, with a block editor and a REST API for headless use.
WordPress manages content, media, users and taxonomies through an administration interface, rendering the public site through a theme and extending behaviour through plugins that hook into a documented event system. The block editor composes pages from reusable blocks, and full site editing extends that model to headers, footers and templates in themes that support it. A REST API exposes the same content for decoupled front ends. A first deployment supplies database credentials through the environment, completes the installation screen and publishes one page.
You know it worked when
- The installation screen completes and the administrator can sign in.
- A published page renders on the public site.
- An uploaded image appears in the media library and on the page.
- A plugin installs and activates without error.
- The site and its media survive a container restart with both volumes persisted.
Known sharp edges
- The site URL is stored in the database and used to build links, so moving the deployment to a different address without updating it produces redirect loops.
- Plugins execute with the application's full privileges, and an abandoned or compromised plugin is the most common route to a compromised site.
- Uploaded media lives on the filesystem while everything else lives in the database, so a backup covering only one of the two cannot restore the site.
- Automatic core updates are enabled by default and can change behaviour on a container that was expected to be static.