Publish an Environment

Preview, validate, publish, and smoke-test a standalone Environment.

On this page

Import and validate locally

Terminal

flt env pull "file://$PWD/environment.yml" env-local --eager
fleet-runtime env preview env-local
fleet-runtime env check env-local

env preview is allocation-free. It shows endpoints, expected tools, startup policy, seeds, image provenance, command, and working directory. env check prepares the Environment, waits for health, validates tools and HTTP endpoints, then tears it down.

Publish the exact root

Terminal

flt env push env-local \
  registry-alpha.fleetai.me/acme/evals/environments/browser:v1 --dry-run

flt env push env-local \
  registry-alpha.fleetai.me/acme/evals/environments/browser:v1

Fresh-pull and serve

Terminal

flt env pull \
  flt://registry-alpha.fleetai.me/acme/evals/environments/browser:v1 \
  env-release
fleet-runtime env serve env-release

In Registry, browse Environments → project → repository. The standalone source digest and a Task-bound prepared or effective Environment digest may differ; use the Task's Environment lineage to compare them.