Global environment-variable profile switcher — think "iHosts, but for env vars".
Switch a whole group of environment variables (dev / staging / prod database credentials, API keys, …) with one command, globally. Your scripts and tools stay completely unaware — they just read env vars as usual. No per-command prefix, no per-directory setup.
$ envsw use myapp prod
myapp → prod (new shells/processes pick it up; open interactive shells refresh before the next command)
⚠ production profile active — every new command now targets prod; switch back with envsw use myapp dev
$ envsw list
myapp
○ dev
● prod (active)Existing tools solve a different shape of this problem:
- direnv / shadowenv switch env by directory, not by environment, and rely on interactive-shell hooks (they often don't fire in non-interactive shells, e.g. commands run by editors or AI agents).
- envchain / dotenvx / dotenv-cli require a prefix on every command (
dotenvx run -f .env.prod -- cmd).
envsw takes the iHosts approach instead: a global state file (a current symlink per group) plus a tiny shell hook. Flip the switch once; every new shell and process picks it up automatically, and already-open interactive zsh/bash shells refresh before the next command.
One-line install:
curl -fsSL https://raw.githubusercontent.com/postdare/envsw/main/install.sh | bashOr install from a local clone:
git clone https://github.com/postdare/envsw.git
cd envsw && ./install.shThe installer copies envsw to ~/.local/bin and appends or upgrades the auto-load hook in ~/.zshenv (zsh) or ~/.bashrc (bash). Or install the binary manually:
install -m 755 envsw ~/.local/bin/envswThe canonical hook snippet lives in install.sh; it loads active profiles at shell startup and refreshes interactive shells before each command.
envsw edit myapp dev # create/edit a profile in $EDITOR (KEY=VALUE lines)
envsw edit myapp prod
envsw use myapp dev # activate
envsw list # groups & profiles, ● marks active
envsw show [myapp] # active profile contents, values masked
envsw off myapp # deactivate a groupProfiles are plain KEY=VALUE files in ~/.envsw/<group>/<profile>.env (created with 600 permissions):
# myapp / dev
MYAPP_ENV=dev
MYAPP_DB_URL=mysql://user:pass@dev-host:3306/mydb
If ~/.envsw/hooks/<group>.sh exists and is executable, envsw runs it after switching:
~/.envsw/hooks/<group>.sh <group> <profile> # after `envsw use`
~/.envsw/hooks/<group>.sh <group> "" # after `envsw off` (empty profile)
A failing hook prints a warning but never blocks the switch. Typical uses: bouncing a VPN, restarting a local proxy, or notifying other tools when an environment changes. Example — switching VPN together with the profile:
#!/usr/bin/env bash
# ~/.envsw/hooks/myapp.sh
group="$1"; profile="${2:-}"
if [ -z "$profile" ]; then
sudo /usr/local/sbin/ovpn-myapp down # envsw off: tear the tunnel down
else
set -a; source "$HOME/.envsw/$group/$profile.env"; set +a
sudo /usr/local/sbin/ovpn-myapp up "$MYAPP_OVPN_PROFILE"
fiThe hooks directory is reserved: it never shows up as a group in envsw list / envsw show.
- Profiles named
prod/production/online/liveare shown in red, and switching to one prints a warning reminding you to switch back. envsw showmasks values after the first 4 characters.- Profile files and directories are created with
600/700permissions. - Colors are tty-only and respect
NO_COLOR; force withENVSW_COLOR=1.
Environment variables are inherited at process start — nothing can change them inside an already-running child process. envsw use just repoints a symlink (~/.envsw/<group>/current); the shell hook sources every group's current file, so each new shell/process gets the active profile. Already-open interactive zsh/bash terminals reload before the next command, but programs that are already running still need to be restarted.
Set ENVSW_ROOT to relocate the profile directory (default ~/.envsw).
A native macOS menu bar companion lives in app/ — click to switch
profiles, red icon when a prod-like profile is active, built-in profile
editor, and it stays in sync with the CLI automatically.
Download: grab the latest iEnvs-*.zip from the
Releases page, unzip, and
drag iEnvs.app to /Applications. The build isn't notarized (no paid Apple
Developer account yet), so the first launch needs a Gatekeeper bypass:
right-click iEnvs.app → Open → Open in the confirmation dialog.
Or build it yourself:
app/scripts/make-app.sh && open app/build/iEnvs.appRequires macOS 13+ and Xcode command line tools to build.