static when the output is HTML, JavaScript, CSS, and other files rather than a long-running application process. Towbar runs buildCommand in the source context and serves the output directory.
Example manifest
This is the validated example from the Towbarexamples/platform-modes project. Replace the documentation IP, domain, and image choices with values for your environment.
.towbar/apps/static.app.yml
Configure it
The example uses a pinned Node build image and pinned nginx runtime image.spaFallback serves the entry page for client-side routes; headers adds response headers. Set container.port to the runtime image’s listen port, not the build tool’s port.
Keep the output path inside the context and verify it exists after the command finishes. Static and Dockerfile builds can use protected build values; do not bake credentials into generated browser assets.
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.