@envmanager-cli/cli

Official CLI for EnvManager - secure environment variable management for development teams.

Installation

# npm
npm install -g @envmanager-cli/cli

# Homebrew (macOS/Linux)
brew install envmanager/tap/envmanager

Quick Start

# Login to EnvManager
envmanager login

# Pull environment variables
envmanager pull

# Push local changes
envmanager push

# Compare local vs remote
envmanager diff

Commands

| Command | Description | |---------|-------------| | login | Authenticate with EnvManager | | logout | Clear stored credentials | | whoami | Show current user info | | pull | Download variables to .env file | | push | Upload variables from .env file | | diff | Compare local and remote variables | | list | List projects and environments | | config | Manage CLI configuration | | dev | Real-time sync during development | | template | Manage .env templates | | validate | Validate against schema | | completion | Generate shell completion script |

Shell Completion

Enable tab completion for commands, options, and your actual project/environment names.

Homebrew Users

If you installed via Homebrew and have shell completion configured, it works automatically.

npm Users

Add one of these to your shell config:

Bash (~/.bashrc or ~/.bash_profile):

eval "$(envmanager completion bash)"

Zsh (~/.zshrc):

eval "$(envmanager completion zsh)"

Fish:

envmanager completion fish > ~/.config/fish/completions/envmanager.fish

Then restart your shell or run source ~/.bashrc (or equivalent).

Using Friendly IDs

Projects and environments have friendly IDs (like #1, #2) that are easier to use than UUIDs.

# List projects to see their IDs
envmanager list projects
#  #1   my-api (My Organization)
#  #2   my-webapp (My Organization)

# Use friendly ID instead of UUID
envmanager pull --project 1 --environment development

# Also works with names
envmanager pull --project my-api --environment production

Multiple Organizations

If you belong to multiple organizations, use --org to specify which one:

envmanager pull --org "My Company" --project 1 --environment staging

Single-organization users don't need --org - it's auto-selected.

CI/CD Usage

Set ENVMANAGER_API_KEY environment variable for non-interactive authentication:

# GitHub Actions example
- name: Pull env vars
  env:
    ENVMANAGER_API_KEY: ${{ secrets.ENVMANAGER_API_KEY }}
  run: envmanager pull --org "My Company" --project 1 --env production

Note: When using API keys, --org must match the organization the API key was created for.

Documentation

Full documentation available at envmanager.dev/docs/cli

Support

• Documentation: https://envmanager.dev/docs
• Email: [email protected]

License

Proprietary - see LICENSE file. This software requires an active EnvManager subscription.