Role
Required
PHP in the WordPress stack
This page explains what PHP means in the WordPress stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
PHP is included by default and treated as a required part of the WordPress stack.
Base service
PHP (WordPress)
Type
service
Stack fit
How PHP fits into this stack
PHP is included by default and treated as a required part of the WordPress stack.
This stack service is based on PHP (WordPress) and keeps the service-specific setup for WordPress in one place.
It is linked to MariaDB, WP content NFS storage, Mailpit, and Valkey inside the stack.
Version policy
This stack service is limited to 8.5, 8.4, 8.3.
Inclusion
Enabled by default: Yes
Required: Yes
Primary: No
Connections
Derivative services: SSHD
db: MariaDB
wp-content: WP content NFS storage
sendmail: Mailpit
redis: Valkey
Storage
wp-content: 20 GB
Stack-specific technical details
Review the operational capabilities exposed by PHP inside this stack, including backups, imports, configs, settings, cron, actions, storage, and service links where they exist.
Settings
Tune service behavior per environment while keeping one reusable stack baseline.
WordPress root subdirectory
Default value: web.
Cron schedules
Run repeatable background jobs with visible schedules and execution details tied to the stack.
wp cron
Schedule:
0 0 * * *. Command: wp cron event run --due-now --path="${HTTP_ROOT}" --url="${WODBY_PRIMARY_URL}".Volumes
Provision the persistent storage and shared volume relationships the stack expects.
WP content
Size: 10 GB. Shared with WP content NFS storage.
Service links
See how services are wired together so dependencies stay consistent across environments.
WP content storage
Linked to WP content NFS storage. Required.
Redis
Linked to Valkey. Optional.
DBMS
Linked to MariaDB. Required.
Mail Transfer Agent
Linked to Mailpit. Optional.