Browse documentation

Apps and deployments

Deploy project code and distinguish task previews from production Apps.

An App is a named deployment target in a project. It selects source code and runs it through configured builder or runner units. Its current deployment records a build and runtime outcome for a particular source commit; it is not a Job Run or a published Release.

Configure and deploy deliberately

An App can select a branch, an explicit tag ref, or a full commit SHA. A manual deployment resolves the chosen source to an exact commit. A separately enabled App branch trigger can deploy accepted advances of master; configuring a Job's trigger:master does not enable that App trigger. A production trigger therefore delegates deployment authority to whoever can advance that protected branch and must be chosen deliberately.

An App Blueprint is a reusable project-scoped specification of units, their build context, optional dependencies, health checks, environment names, and volume mounts. Merely storing a blueprint does not create an App, claim a host, install secrets, or deploy anything. An App's environment values are write-only; they are not part of a blueprint.

A preview is an isolated, temporary App

A task preview uses the same deployment engine but pins an exact task SHA and one selected blueprint specification. It is not the production App and does not inherit production secrets, storage volumes, or network identity. The current preview slice accepts only stateless blueprints with no required environment values or volumes. Preview addresses are public to anyone who knows the URL, so never use them to show private data.

Previews are leased and disposable. If the task head or blueprint changes, an existing preview does not silently follow them; an authorized person must explicitly update it. The lease can expire and remove the running container and route without changing the task's Git history. A successful task merge or closure also cleans up its preview. App creation, host changes, and other sensitive programmatic actions can require browser confirmation; starting a permitted task preview has its own limited authority instead.

See task turns and review for what the exact task head means, and deploy an existing App for a focused workflow. This page is a model, not a production runbook.