vers env

vers env manages environment variables that Vers injects into new VMs at boot. The variables are written to /etc/environment, so they’re available to SSH sessions and anything launched via vers execute.

vers env only affects newly-created VMs. Existing VMs keep the environment they were booted with.

Synopsis

vers env list                              # Show all configured variables
vers env list --format json                # Machine-readable
vers env set KEY VALUE                     # Set (or update) a variable
vers env delete KEY                        # Remove a variable

Subcommands

`vers env list`

List all environment variables configured for your account.

Option	Description
`--format json`	Machine-readable output

Aliases: ls.

vers env list
vers env list --format json | jq '.[].key'

`vers env set`

Set an environment variable.

vers env set KEY VALUE

Constraints

KEY must be a valid shell identifier: letters, digits, underscores; cannot start with a digit.
KEY is at most 256 characters.
VALUE is at most 8192 characters.

Examples:

vers env set DATABASE_URL postgres://localhost/mydb
vers env set API_KEY secret123
vers env set DEBUG true

`vers env delete`

Remove an environment variable. The key is no longer injected into new VMs; existing VMs are unaffected. Aliases: del, rm, remove.

vers env delete DATABASE_URL
vers env delete API_KEY

How it works

Stored per account

Variables live on your Vers account, not on any single VM.

Injected at VM boot

When a new VM is provisioned (vers run, vers branch, vers run-commit, vers build), the orchestrator writes every variable to /etc/environment before handing the VM over.

Available to sessions and exec

Use cases

Secrets: API keys, database URLs, webhook tokens — available to every VM without leaking into your Dockerfile or vers.toml.
Feature flags: DEBUG=true, FEATURE_X=on.
Per-account defaults: any variable you want every VM you create to inherit.

For secrets you want scoped to a single commit rather than your whole account, bake them into a commit with vers build + ENV or write to /etc/environment in a RUN step.

Common Patterns

Bulk-load from a local .env file

while IFS='=' read -r key value; do
  [ -n "$key" ] && [ "${key#\#}" = "$key" ] && vers env set "$key" "$value"
done < .env

Clear every variable

vers env list --format json | jq -r '.[].key' | xargs -n1 vers env delete

Verify injection on a fresh VM

VM=$(vers run --wait --format json | jq -r .root_vm_id)
vers execute "$VM" -- cat /etc/environment

Overview

Project Commands

Branch Commands

Repository Commands

VM Commands

Environment

Auth Commands

Utility Commands

Synopsis

Subcommands

`vers env list`

`vers env set`

`vers env delete`

How it works

Use cases

Common Patterns

Bulk-load from a local .env file

Clear every variable

Verify injection on a fresh VM

See also

​Synopsis

​Subcommands

​vers env list

​vers env set

​vers env delete

​How it works

​Use cases

​Common Patterns

​Bulk-load from a local .env file

​Clear every variable

​Verify injection on a fresh VM

​See also

Synopsis

Subcommands

`vers env list`

`vers env set`

`vers env delete`

How it works

Use cases

Common Patterns

Bulk-load from a local .env file

Clear every variable

Verify injection on a fresh VM

See also