Environment variable management for developers

Environment variables are configuration, not source code

Apps read process.env (or framework equivalents) so the same build can run against different databases, APIs, and feature flags. The hard part is distributing the right values to the right people and machines.

Per-environment isolation

EANVI models named environments inside each project. Development can use sandbox keys while production keeps live credentials — without maintaining three conflicting .env files by hand.

From .env files to a managed workflow

Import an existing dotenv file, invite the team, then pull with the CLI. Local runtimes keep using familiar env files; the encrypted workspace prevents drift and Slack archaeology.

eanvi pull
# refreshes local env from the bound environment

When an environment variable is a secret

If a value grants access or exposes private data, treat it as a secret: encrypt it, audit reveals, and restrict production roles. Public non-sensitive flags can still live in ordinary config when appropriate.