WordPress stack
Services included in stack
Name | Versions | Enabled by default | Required |
---|---|---|---|
Varnish (WordPress) | 6.0 | ||
PHP (WordPress) | 8.3 | ||
SSHD (derivative) | |||
Nginx (WordPress) | 1.27, 1.25 | ||
Ganesha NFS provisioner | 4 | ||
MariaDB | 11.4, 11.2 | ||
Valkey | 7.2 | ||
Mailpit | 1.20 | ||
Gotenberg | 8 | ||
OpenSMTPD | 7 | ||
Cloud MariaDB | 10.3 | ||
Cloud MySQL | 5.7, 8 |
- additional services can be added and deleted
- when one of the services updated the stack can be upgraded
- update stack configuration and apply changes to all app instances
Deploy WordPress to managed Kubernetes in a few clicks
Connect your own account from cloud providers and let Wodby to spin up Kubernetes cluster with all infrastructure needed to run WordPress.
Build WordPress with your own codebase by connecting a repository from the git hosting
Connect your own account from the following git providers and select your repository to be connected with the buildable service to be in used in CI.
Use CI solutions to build your WordPress app
By default we offer integrated Wodby CI that knows your stack. Or use our Wodby CLI together with your CI service to build your WordPress app, it already knows your stack.
Use third-party SMTP services for guaranteed email delivery
OpenSMTPD can use third-party SMTP services as relay for reliable email delivery.
Store your WordPress container images securely in a private Docker registry
Out of the box we provide private docker registry with a limited storage for free.
Use managed Database solutions for your WordPress app
You can chose to use managed database service instead of running database in a container for extra reliability. For that we have special "external" services (Cloud MariaDB, Cloud MySQL) that integrate with third-party database services.
Integrate your WordPress app with the third-party services
Add secrets and environment variables to your WordPress app, manage all your integrations with third-party services from your stack.