Apps

ENV Manager

Environment variables stored in the macOS Keychain and exported as .env files.

Think of ENV Manager as a password manager for your .env files. The variable names are ordinary data; the values live in the macOS Keychain — never in a plaintext file the next grep could stumble into.

Decorative animation of ENV Manager. Step-by-step instructions follow in the text below.

Create an environment

  1. Open ENV Manager from the sidebar.
  2. Click New Environment and name it after the thing it configures: my-app · production, staging, local.
  3. You can keep as many environments as you like, each with its own set of keys.

Add variables

  1. Select an environment.
  2. Add a key (DATABASE_URL, STRIPE_SECRET_KEY, …) and its value.
  3. The value goes straight into the macOS Keychain. The app's own files only remember the key names and their order — the secrets themselves are the Keychain's problem (and it's very good at that job).

Reveal a value

Click the reveal control on any variable, and macOS asks for Touch ID or your password — every single time.

Why every time? Because a revealed secret is a plaintext secret on screen. The prompt makes "showing a secret" a deliberate act, not something that happens because you left a window open.

Export a .env file

  1. Select the environment.
  2. Click Export .env.
  3. Authenticate (Touch ID / password — same reason as reveal: a .env file is plaintext).
  4. Choose where to save it. You get a standard KEY=value file, ready for your project.

Tip

Treat exported .env files as disposable: export, use, delete. The durable copy of your secrets is the one in the Keychain.