Skip to main content

​
The Core Command

The CLI reads config.yaml, resolves the effective branch, builds an image, and creates a new version for the matching environment.

​
The Deployment Model

Every deploy creates a new version. A branch points at the current active version.

​
Branch Resolution

For tu deploy, the branch comes from:
  1. --branch, if provided
  2. the current git branch
  3. fallback logic when git context is unavailable
The platform then resolves that branch to an environment using branch rules. In a default setup:

​
config.yaml

​
Task Stickiness

areTasksSticky controls what happens to running tasks during a rollout. If you need to move running tasks later, use tu tasks migrate.

​
Environment Secrets

Runtime secrets are environment-scoped. Use tu env add to set them and tu env ls, tu env get, tu env rm, tu env pull, and tu env import to manage them. Your code reads them through normal environment variables:

​
Rollback

Use tu rollback to move a branch back to an earlier version.
Rollback uses the target version’s secret snapshot. Pending environment-secret changes are not rewritten by the rollback.

​
Deployment History

Use tu ls to inspect version history and branch events:
Use tu logs to inspect runtime behavior:

​
Useful Flags

​
Remote Builds

Remote build mode is controlled by the CLI runtime, and when enabled it builds remotely instead of locally. One important constraint: remote builds are linux/amd64 only. See CLI Reference for command details.