Laravel application stack for Kubernetes on Wodby

Deploy Laravel applications on Kubernetes with Wodby.

This repository defines the Wodby stack manifests and default service composition for Laravel.

Stack contract

• Laravel stack on Wodby
• Browse Wodby application stacks
• Wodby stack documentation
• Stack manifest reference

Start from a boilerplate

Use one of the compatible boilerplates exposed by this stack's services to start with Wodby CI build configuration:

• Laravel on Wodby

Service definitions

• PHP (Laravel) service
• Nginx (Laravel) service
• MariaDB service
• Ganesha NFS provisioner service
• Valkey service
• Mailpit service
• OpenSMTPD service
• Gotenberg service
• Cloud MariaDB service
• Cloud MySQL service

What's included

Component / service	Default configuration
PHP php	required; enabled by default; volumes: storage 20 GB; links: db → mariadb, redis → valkey, storage → files-nfs, sendmail → mailpit
Nginx nginx	required; enabled by default; links: backend → php
MariaDB mariadb	required; enabled by default; volumes: data 10 GB
Files NFS storage files-nfs	optional; enabled by default; volumes: data 25 GB
Valkey valkey	required; enabled by default
Mailpit mailpit	optional; enabled by default
OpenSMTPD opensmtpd	optional; disabled by default
Gotenberg gotenberg	optional; disabled by default
Cloud MariaDB cloud-mariadb	optional; disabled by default
Cloud MySQL cloud-mysql	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.

Validate the stack manifest

wodby stack validate-manifest stack.yml --org <org-id>

Deploy this stack

Start from Laravel on Wodby, which includes .wodby/pipeline.yml, 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.

Maintain a custom version

1. Fork this repository.
2. Edit the stack manifest.
3. 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.