Build and run PHP (WordPress) applications on Kubernetes with Wodby.
This repository defines the Wodby service manifests and operational configuration for PHP (WordPress).
Use one of the boilerplates exposed by this service to start with compatible build configuration and Wodby CI:
| Property | Manifest configuration |
|---|---|
| Service name | wordpress-php |
| Type | Application service |
| Inherits from | php with version constraint ^1.0.0 |
| Versions | 8.5 by default; also available: 8.4, 8.3, 8.2 |
| Workloads | main (Deployment, primary) |
| Containers | php using wodby/wordpress-php, build target |
| Endpoints | None |
| Service links | WP content storage (wp-content), required; Redis (redis), optional |
| Application build | Git source connection enabled; Dockerfile: Dockerfile; boilerplates: Vanilla WordPress |
| Configuration and operations | 1 settings, 1 volumes, 1 cron schedules |
Use this service through WordPress application stack, or reference wordpress-php from
a custom Wodby stack.
A service is a reusable component and does not deploy by itself. The stack defines its links, settings, versions, resources, and relationship to the rest of the application.
- Fork this repository.
- Edit the service manifest and referenced files.
- Import the repository as a Git-backed service.
- Reference the service from a stack manifest.
Keep service, workload, container, endpoint, link, volume, config, and derivative names stable unless dependent stacks and app-level overrides are updated at the same time.
Validate the manifests with:
wodby service validate-manifest service.yml --org <org-id>See the service manifest reference and the managed services index.