Skip to main content
Choose nixpacks for projects that already rely on Nixpacks configuration. The declaration pins its version and image, chooses a repository context, and can point at nixpacks.toml.

​
Example manifest

This is the validated example from the Towbar examples/platform-modes project. Replace the documentation IP, domain, and image choices with values for your environment.
.towbar/apps/nixpacks.app.yml

​
Configure it

The example makes the builder architecture explicit and enables workload-scoped caching. After the first deployment, inspect the built image and health check instead of assuming that source detection chose the expected start command. Nixpacks builds reject build secrets. For private build-time dependencies, switch to a Dockerfile with a protected BuildKit secret mount. Map the named environment to a branch, register and prepare its server, then sync the repository. Start with a manual deployment and verify the running service before opting into automation. See Application manifest for shared fields and Deployment modes to compare modes.
Last modified on September 26, 2026