Docs
Migrating from .env files
Import existing dotenv files into Eanvi without breaking local workflows.
Migrating from .env files
Move the source of truth from shared files to Eanvi while keeping a local .env as a checkout for runtimes that still expect one.
1. Inventory
Collect the env files you actually use:
.env,.env.local,.env.development,.env.production- CI variable lists
- Secrets sitting in password managers or chat history
Deduplicate keys. Decide which environment each file belongs to.
2. Create project structure
- Create an organization and project.
- Add environments (
development,staging,production). - Ensure
.env*remains gitignored.
3. Import
Dashboard
Environment → Import → paste or upload → preview → confirm.
CLI
eanvi login --api-key "$EANVI_API_KEY"
eanvi init --project my-app --environment development
eanvi import .env --dry-run
eanvi import .env
eanvi import .env.production --environment production
4. Replace distribution
| Before | After |
|---|---|
Paste .env in Slack | Invite teammate + eanvi pull |
Commit .env.example only | Keep .env.example for key names; values from Eanvi |
| CI copies from a private gist | CI uses API key + eanvi pull |
5. Verify
eanvi diff
eanvi doctor
eanvi list
Boot the app once with a fresh pull. Compare against the old file with diff if needed — then delete shared copies.
6. Optional cleanup
- Rotate any values that were previously exposed in chat or git history.
- Revoke old tokens after import.
- Document the new onboarding path in your README (
eanvi login→eanvi pull).