Runtime Environments

Overview

The Environments section in Fly Web gives your team visibility into what’s running across all your runtime environments. See which images and releases are active, review deployment history, and manage environment tokens.

Environment Dashboard

The dashboard provides a unified view across all your environments.

For each environment, you can see:

  • Environment name and description
  • Releases pulled: the latest release pulled by the environment, along with the images included in it and the pull timestamp. If an image was pulled locally (not from a CI release), it appears as “Pulled Locally”

Environment Deep Dive

Select any environment from the dashboard to view its full profile.

Releases Pulled

A chronological log of all releases pulled by this environment. For each release, Fly shows you:

  • The release version and AI-generated summary
  • The PRs and commits included in that release
  • The images pulled as part of the release

Token Tracking

View the tokens associated with this environment:

  • Number of active tokens
  • Token names and their last usage timestamps

Create an Environment

You can create environments from Fly Web or from your IDE.

From Fly Web:

  1. Navigate to the Environments section
  2. Click Create Environment
  3. Provide a name (lowercase letters, numbers, and hyphens) and an optional description
  4. Fly suggests generating a token to connect the environment right away

Update

Update an environment’s name or description at any time. Updates don’t affect active tokens or historical consumption data.

Delete

Deleting an environment requires explicit confirmation. Once deleted, all associated tokens are automatically revoked and the environment will no longer track consumption.

Connect Your Environment

Environment-scoped tokens are the secure bridge between Fly Registry and your runtime.

Generate a Token

Tokens can be generated during environment creation or at any time from the environment profile.

Apply the Pull Secret

After generating a token, Fly provides a ready-to-use image pull secret. Copy it from the token popup and apply it to your runtime namespace:

kubectl create secret docker-registry fly-registry-secret \
  --docker-server=<your-fly-subdomain>.jfrog.io \
  --docker-username=<token-username> \
  --docker-password=<your-token> \
  --namespace=<namespace>

Once the pull secret is applied, your environment is connected. Fly will start tracking every image pull, and you’ll see releases and images appear in the environment dashboard.

Revoke a Token

You can revoke a token at any time from the environment profile. Once revoked, any runtime using that token will be denied access to Fly Registry.

Next Steps