Build and run PHP applications on Kubernetes with Wodby.
This repository defines the Wodby service manifests and operational configuration for PHP.
Use one of the boilerplates exposed by this service to start with compatible build configuration and Wodby CI:
| Property | Manifest configuration |
|---|---|
| Service name | php |
| Type | Application service |
| Versions | 8.5 by default; also available: 8.4, 8.3, 8.2 |
| Workloads | main (Deployment, primary) |
| Containers | php using wodby/php, build target |
| Endpoints | fpm: TCP 9000 (main) |
| Service links | DBMS (db), optional; Mail Transfer Agent (sendmail), optional |
| Application build | Git source connection enabled; Dockerfile: Dockerfile; boilerplates: Composer boilerplate |
| Helm | chart oci://registry-1.docker.io/wodby/php-fpm; version 0.3.3 |
| Configuration and operations | 1 integration slots |
Use this service through PHP application stack, or reference 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.
On Wodby installations with development workspaces enabled, this service can run
against a persistent Git checkout at /var/www/html. Its personal SSH runner uses
the selected PHP runtime, Git and Composer, with a separate persistent home at
/home/wodby. Preparation runs composer install when composer.json exists.
Connect a repository when creating the workspace and select shared RWX storage. Use your Wodby account's SSH public key to connect. Git push credentials and agent authentication are configured separately inside your private workspace home. Changes affect the development environment; commit and push them before building and deploying a Standard environment. Restarting or resuming does not pull Git or replace your checkout. Applications requiring additional operating-system packages must provide a compatible runtime image.