The Core Command
config.yaml, resolves the effective branch, builds an image, and creates a new version for the matching environment.
The Deployment Model
| Resource | Meaning |
|---|---|
Environment | A named policy such as production or preview |
Branch | A branch-specific deployment slot |
Version | One deployed build of your agent |
Branch Resolution
Fortu deploy, the branch comes from:
--branch, if provided- the current git branch
- fallback logic when git context is unavailable
| Branch | Environment | Config section |
|---|---|---|
main | production | deployment.production |
| other branches | preview | deployment.preview |
config.yaml
Task Stickiness
areTasksSticky controls what happens to running tasks during a rollout.
| Setting | Behavior |
|---|---|
true | Running tasks stay on the version they started on |
false | Running tasks can migrate during rollout |
tu tasks migrate.
Environment Secrets
Runtime secrets are environment-scoped. Usetu 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
Usetu rollback to move a branch back to an earlier version.
Deployment History
Usetu ls to inspect version history and branch events:
tu logs to inspect runtime behavior:
Useful Flags
| Command | Common flags |
|---|---|
tu deploy | --config, --branch, --skip-build, --no-cache, --yes, --verbose, --detach |
tu rollback | --branch, --version, --agent, --config, --yes, --json |
tu logs | --task, --level, --source, --since, --until, --version, --limit, --follow |
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 arelinux/amd64 only.
See CLI Reference for command details.