Configuration

ev.yaml

ev.yaml is created by ev init at the root of your git repository and should be checked into version control. It defines the project boundary and provides default context so you don't have to pass flags on every command.

Minimal Config

project: clxxxxxxxxxxxxxxxxxxxxxxxx
default_env: dev

That is all you need for a single-app project. ev treats the repo root as the one app.

All Fields

Field	Type	Required	Description
`project`	string	Yes	Project ID assigned by the ev server during `ev init`.
`default_env`	string	No	Environment used when no environment is specified. Defaults to `dev`.
`apps`	map	No	Named apps for monorepos. Each entry has a `path` field.
`backend`	object	No	Storage backend configuration (type, region, prefix).
`environments`	map	No	Per-environment backend overrides.

Monorepo Config

project: clxxxxxxxxxxxxxxxxxxxxxxxx
default_env: dev
 
apps:
  frontend:
    path: packages/frontend
  backend:
    path: packages/backend
  worker:
    path: packages/worker

When you run ev commands from packages/backend/, ev automatically resolves the app to backend. You can override with colon syntax:

ev push                    # auto-detected from cwd
ev push backend:staging    # explicit app and environment
ev pull frontend:prod      # explicit app and environment

Backend Config

project: clxxxxxxxxxxxxxxxxxxxxxxxx
default_env: dev
 
backend:
  type: aws-secrets-manager
  region: us-east-1
  prefix: /myapp/

See Storage Backends for all backend types and options.

Per-Environment Backend Override

Keep dev on ev's encrypted storage while prod uses AWS Secrets Manager:

project: clxxxxxxxxxxxxxxxxxxxxxxxx
default_env: dev
 
backend:
  type: aws-secrets-manager
  region: us-east-1
  prefix: /myapp/
 
environments:
  dev:
    backend:
      type: ev

Context Resolution

When you run an ev command, it resolves context in this order:

Explicit argument — ev push backend:staging sets app to backend, env to staging
Partial argument — ev push staging sets env to staging, app from cwd or ev.yaml
Working directory — if cwd matches an app path in ev.yaml, that app is used
default_env — from ev.yaml
Global default — dev

Local Files

ev stores per-user state in ~/.config/ev/:

File	Contents
`~/.config/ev/auth.json`	Auth token from `ev login`
`~/.config/ev/keys.json`	Your local keypair (Curve25519 public + private key)
`~/.config/ev/config.json`	API URL and other client settings

These files are created automatically and should never be checked into version control. ev adds them to .gitignore during ev init.

Configuration

On this page