Setting up builders

Builds run on a builder. You need one to deploy from Git. Manage them under Builders.

On a fresh install, Pyo adds a builder on the server it runs on, named after that server. You can remove or replace it like any other builder.

Where a builder can runCopy Anchor Link

Choose Add builder, then where it runs:

• This machine: the server Pyo runs on, alongside Pyo.
• In a cluster: another server in one of your clusters, sharing that machine with your services.
• New server: a dedicated build server. Run the command Pyo shows on the machine, and it joins a cluster as a build-only server. Nothing else runs there, so heavy builds don't slow your services down.

Each server runs at most one builder.

Remove a builderCopy Anchor Link

Choose Remove builder from its menu. A builder in a cluster takes its build cache with it, and builds running on it fail. On a build-only server, the builder stops and the server stays in its cluster. Remove the server too if you don't need it.

How it worksCopy Anchor Link

A builder runs BuildKitThe build engine behind Docker. It turns your code or Dockerfile into an image. and connects out to Pyo with its own token. It picks up build jobs, streams the logs and hands back the finished image.

BuildKit only runs while there are builds, so an idle builder uses almost no memory. A build starts it, and its log shows Starting the builder… for the few seconds that takes. After 10 minutes without builds, it stops again. The build cache stays on the server's disk, so the next build is as fast as before.