Deploy PHP applications on Kubernetes with Wodby.
This repository defines the Wodby stack manifests and default service composition for PHP.
- PHP stack on Wodby
- Browse Wodby application stacks
- Wodby stack documentation
- Stack manifest reference
Use one of the compatible boilerplates exposed by this stack's services to start with Wodby CI build configuration:
- PHP service
- Nginx (PHP) service
- MariaDB service
- Apache HTTP server (PHP) service
- PostgreSQL service
- Valkey service
- Mailpit service
- OpenSMTPD service
- Gotenberg service
| Component / service | Default configuration |
|---|---|
PHPphp |
required; enabled by default; links: db → mariadb, sendmail → mailpit |
Nginxnginx |
required; enabled by default; links: backend → php |
MariaDBmariadb |
optional; enabled by default; volumes: data 20 GB |
Apache HTTP serverhttpd |
optional; disabled by default; links: backend → php |
PostgreSQLpostgres |
optional; disabled by default; volumes: data 20 GB |
Valkeyvalkey |
optional; disabled by default |
Mailpitmailpit |
optional; enabled by default |
OpenSMTPDopensmtpd |
optional; disabled by default |
Gotengergotenberg |
optional; disabled by default |
Enabled optional services are selected by default but can be excluded when an app is created. Disabled optional services are available but not selected by default. Required services cannot be excluded.
wodby stack validate-manifest stack.yml --org <org-id>Start from Composer boilerplate, or connect your own compatible source repository.
Review service versions, storage, links, and optional components when creating the application. The same stack can be reused across development, staging, and production environments.
- Fork this repository.
- Edit the stack manifest.
- Import the repository as a Git-backed stack.
When replacing or renaming a stack service, update every related link target and derivative reference. Stack-local names and referenced service names are distinct identifiers.