Runtime
Executes PHP requests
WordPress PHP files are loaded by phrust-server as the request handler, including the front controller and theme templates.
Actual WordPress, executed by Phrust
WordPress running on a Rust PHP runtime.
This page is rendered by WordPress through phrust-server. The theme, templates, WordPress bootstrap, database reads, and static assets all flow through the Phrust demo stack.
What Phrust is
A compatibility-focused PHP runtime and HTTP server written in Rust.
Phrust is building the execution path needed to run PHP applications without delegating requests to PHP-FPM, CGI, Apache modules, or the native PHP CLI. The WordPress demo keeps that boundary visible.
Database
Talks to MariaDB
The demo uses WordPress' normal database tables and a mysqli smoke endpoint to prove a real database roundtrip.
Honesty
Surfaces gaps
If WordPress reaches unsupported runtime behavior, the demo is meant to expose that as a Phrust compatibility task.
Request path
One runtime path, no PHP fallback.
The Compose stack runs only phrust-server and MariaDB for the default HTTP path. The WordPress files are unmodified core plus this demo theme.
01 HTTPThe browser requests the WordPress front controller on port 8080.
02 Phrustphrust-server resolves the PHP script, executes WordPress, and serves static assets from the same docroot.
03 WordPressWordPress loads the active phrust-demo theme and asks MariaDB for options, pages, and posts.
04 ResponseThe rendered HTML and theme CSS are returned from the Phrust runtime.
What this demo proves
A real WordPress page with a real theme.
Custom themeHeader, footer, front-page template, page templates, and CSS are loaded by WordPress.
Seeded siteThe home page, notes, runtime page, and compatibility page are installed deterministically.
Static assetsThe Phrust logo and theme stylesheet are served from the WordPress theme directory.
Database contentWordPress options and post records come from MariaDB, not from a static HTML mock.