Skip to main content

​
Deployments

A deployment is a single GitHub repository. It stores shared settings and gives the dashboard and CLI one place to inspect or update those instances together.
Dashboard view of a deployment showing aggregate instance counts

A deployment of the hello-world example with two running instances.

Each container instance in a deployment group is an independent enclave with its own name, status, resources, domain, and lifecycle. A deployment does not add load balancing or automatically update its instances when a release is published. The dashboard shows each deployment with aggregate counts for running, deploying, failed, and stopped instances.
Dashboard view of a deployment expanded to show individual container instances

Both instances run the same repo and tag but have different names.

Repository-scoped secrets belong to this deployment namespace. They are available only to containers using that repository and move with it when the repository is renamed. If Tinfoil merges an existing destination namespace for the same repository, resolve duplicate secret names before the rename can complete. A destination belonging to a different repository is isolated and never merged.

​
Inspecting a deployment

Use either the deployment UUID or its owner/repo name:
Pass -o json for machine-readable output. To set the staging mode used by default for new instances and deployment-wide updates:
Manage secrets for the same repository with tinfoil repo secret list owner/repo. See Secrets & environment variables for scope and naming rules. See Updating & lifecycle to update every instance, or a selected set, to the same release.

​
Container lifecycle

Individual containers move through these backend states. The dashboard presents Ready as Running: The dashboard polls for status updates automatically and updates the deployment counts. For updating a running container, rolling back, canceling an in-progress update, or recovering from a failed update, see Updating & lifecycle.

​
Stopping and starting a container

Open a container’s actions in the dashboard and click Stop to shut down its enclave without deleting its saved configuration. Click Start to deploy it again with the saved settings. The start dialog also lets you select updated settings before deployment.

​
Deleting a container

Click Delete on a container to permanently remove it. This:
  • Stops the running enclave
  • Cancels any in-progress update
  • Deletes the container’s secret bindings
  • Removes the container from your org
Deletion is irreversible. The container’s configuration, secret bindings, and environment variables are permanently removed.

​
Using the CLI

The Tinfoil CLI exposes both deployment-level inspection and the individual container lifecycle:
See the CLI reference for create flags, update controls, and scripting tips.