CLI workflows

Onboard a new machine

eanvi login
cd ~/code/my-app
eanvi init --project my-app --environment development
eanvi pull
eanvi doctor

For non-interactive auth, use eanvi login --api-key "$EANVI_API_KEY". Start the app against the freshly written .env.

Daily edit loop

1. Change values locally in .env, or in the dashboard.
2. Preview:

eanvi diff
eanvi push --dry-run

1. Apply:

eanvi push
# or pull remote wins
eanvi pull --force

Bidirectional sync

When both local and remote changed:

eanvi sync --dry-run
eanvi sync --yes

Use --force only when you intentionally want local values to win conflicts.

Promote secrets between environments

Export from staging, import into production carefully:

eanvi export -e staging --format env --output /tmp/staging.env
eanvi import /tmp/staging.env -e production --dry-run
eanvi import /tmp/staging.env -e production
rm /tmp/staging.env

Prefer copying individual keys in the UI when only a subset should move.

CI pull before build

eanvi login --api-key "$EANVI_API_KEY" --org acme
eanvi pull --project my-app --environment production --output .env --force
npm run build

See the full CI/CD guide.

Incident: bad value shipped

1. Open secret history in the dashboard.
2. Restore the previous version (or reveal historically for forensics).
3. eanvi pull --force on affected machines.
4. Review Audit Activity for who changed what.

Diagnose failures

eanvi doctor --verbose
eanvi whoami
eanvi list

Common fixes: wrong --org, expired API key, missing eanvi init, API URL pointing at the wrong environment.