Static site - Towbar

Related reading: Example. context: . means the repository root. The build command must produce the declared output directory; adapt it to the actual project.

Towbar manifest

.towbar/services/static-site.service.yml

id: static-site
name: Static site
deployment:
  type: static
  context: .
  output: dist
  buildCommand:
    - npm
    - run
    - build
  nodeImage: node:24-alpine@sha256:50c8e8ca1d27439048670df5883f32d57cf81cff6233222c893fd0d9884cbd81
  runtimeImage: nginxinc/nginx-unprivileged@sha256:27985295bdb22a1ef8f712863210bd5877c0f3006494a593e86b3fe0fa55467e
  headers:
    Cache-Control: public, max-age=300
    X-Content-Type-Options: nosniff
container:
  port: 8080
health:
  path: /
environments:
  production:
    server: 192.0.2.10

Configure

Register and prepare the example server or servers, connect the repository, and map production to the branch containing these files.
Sync the repository, inspect the resolved configuration, deploy manually, and perform the verification below before enabling automation.

Verify

The output directory exists and the runtime listens on the declared port. For field constraints, see Service manifest.

Last modified on September 27, 2026