Environments

An environment is an isolated runtime context inside a project. A typical setup has production, staging, and dev environments. Services, deployments, and variables are all scoped per environment.

All environment commands require a workspace and project. Set them with edge workspace use / edge project use or pass --workspace/-w / --project/-p.

list

List all environments in the active project. The active environment is marked with *.

edge env list
edge env list --workspace acme-corp --project payments --json

Example output

    SLUG        NAME
*   production  Production
    staging     Staging
    dev         Development

create

Create a new environment.

edge env create <name>

edge env create "Staging"

use

Set the active environment. Saved to ~/.simplifyd/config.json.

edge env use <slug>

edge env use staging

Once set, all service, deployment, and variable commands default to this environment. Override per-command with --env/-e.

Tip: use edge link instead

If you work from a specific directory, edge link is often more convenient than setting the active workspace/project/env globally:

cd ~/code/payments-api
edge link --workspace acme-corp --project payments --env production

This writes a .edge.json in the current directory. Any edge command run inside this directory tree picks up that context automatically. See edge link.