Stacks/HTML/CI/CD

CI/CD for the HTML stack

The HTML stack provides compatible public boilerplates, so teams can start from a working foundation instead of wiring builds from scratch.

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

Public boilerplates

Start from a compatible public boilerplate 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 starting from a public boilerplate.

CI providers

Wodby CI supports the public boilerplates, 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.