CPU-bound process - Towbar

Related reading: Container and health. context: . means the repository root. The source project, start command, and health endpoint must match the selected build mode.

Towbar manifest

.towbar/services/cpu-bound-process.service.yml

id: cpu-bound-process
name: CPU-bound process
deployment:
  type: dockerfile
  context: .
  dockerfile: Dockerfile
container:
  port: 3000
  resources:
    cpus: 2
    memory: 2g
health:
  path: /health
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 target server has capacity for the new and old copies during rollout. For field constraints, see Service manifest.

Last modified on September 27, 2026