CI/CD for the Laravel stack

We already provide public build templates with a Wodby CI pipeline for the Laravel stack, so teams can start from a working boilerplate instead of wiring builds from scratch.

PHP can build from source inside the stack. Connect your own Git repository, fork one of our public templates, or keep the same stack and use external CI and registries where that fits your workflow.

Public build templates

Fork one of these public templates to start with a working boilerplate and Wodby CI pipeline instead of an empty repository.

Connect repositories, CI providers, and registries

Git providers connect source code, Wodby CI handles stack-aware builds out of the box, external CI can fit the same stack model, and registries store the resulting images.

Connect your Git repository

Use a supported Git provider when you want to build from your own repository instead of forking one of the public templates.

CI providers

Wodby CI is already included in the public templates, and you can still plug in another CI provider when that fits your workflow better. External pipelines can call Wodby CLI to run the same stack-aware init, build, release, and deploy flow from your stack data.

Container registries

Keep built images in Wodby Registry by default or switch to an external registry without changing the stack-aware release flow.