Container and health

The container block describes how the deployed image runs. port is the port inside the container; the process must listen on the container’s network interface. Set resource limits near the port so a reviewer can assess expected capacity:

.towbar/services/web.service.yml

container:
  port: 3000
  resources:
    cpus: 1
    memory: 1g
health:
  path: /health
  timeoutSeconds: 60

The HTTP health path should respond without interactive authentication. A successful build is not sufficient for traffic promotion: Towbar waits for the candidate to pass readiness. Allow enough time for startup, but investigate a consistently slow start rather than raising the timeout indefinitely.

Private connectivity

Set the same container.network on a Service and Datastore on the same server. A Datastore’s ID is its network alias unless it sets networkAlias:

.towbar/services/web.service.yml

container:
  port: 3000
  network: application

For a PostgreSQL datastore with alias postgres, the Service can connect to postgres:5432. Put the credential-bearing URL in a service runtime secret, not in the manifest. A Docker network on one host does not connect containers across different servers.

Persistent storage

Use a Docker-managed named volume when a process must retain files across replacement:

.towbar/services/files.service.yml

rollout:
  type: recreate
  maintenanceMode: true
  reason: The service uses a single-writer volume
container:
  port: 3000
  volumes:
    - name: uploads
      mountPath: /app/uploads
      initialData: image

Create the mount directory in the image with ownership for its runtime user. Volumes survive redeployments and image rollback, remain on their server, and are not backed up by Towbar. initialData applies only when adding a new volume: previous-container imports from the stopped container, while image initializes from the new image. Environment overrides replace the common volume list. Host-directory bind mounts are not accepted; keep backups of important files outside Towbar.

Servers

Repositories

Services

Datastores

Secrets

Deployments and access

Container and health

Private connectivity

Persistent storage

​Private connectivity

​Persistent storage

Private connectivity

Persistent storage