@lockr-dev/cli
v1.0.1
Published
Command-line interface for Lockr secrets management - securely pull, sync, and inject environment variables
Maintainers
Readme
Lockr CLI
A command-line interface for managing secrets with LockrDev.
Installation
npm install -g @lockr-dev/cli
# or
npx @lockr-dev/cliAuthentication
First, create an API token in the Lockr dashboard:
- Go to Integrations → API Tokens (Pull)
- Click Create API Token
- Copy your token
Then authenticate:
lockr auth login --token YOUR_API_TOKEN
# or set the environment variable
export LOCKR_API_TOKEN=YOUR_API_TOKENCommands
Pull Secrets
Pull secrets from Lockr to your local environment:
# Pull all secrets for production
lockr pull --env production
# Pull to a specific file
lockr pull --env production --output .env
# Pull specific keys only
lockr pull --env production --keys API_KEY,DATABASE_URL
# Output as JSON
lockr pull --env production --format jsonRun with Secrets
Run a command with secrets injected as environment variables:
# Run your app with production secrets
lockr run --env production -- npm start
# Run with staging secrets
lockr run --env staging -- docker-compose upList Environments
lockr envs listWhoami
Check your current authentication:
lockr whoamiConfiguration
Create a .lockrrc file in your project root:
{
"project": "my-project",
"defaultEnv": "development"
}CI/CD Usage
GitHub Actions
steps:
- name: Pull secrets
run: npx @lockr-dev/cli pull --env production --output .env
env:
LOCKR_API_TOKEN: ${{ secrets.LOCKR_API_TOKEN }}GitLab CI
deploy:
script:
- npx @lockr-dev/cli pull --env production --output .env
- docker build -t myapp .
variables:
LOCKR_API_TOKEN: $LOCKR_API_TOKENCircleCI
jobs:
build:
steps:
- run:
name: Pull secrets
command: npx @lockr-dev/cli pull --env production --output .envEnvironment Variables
| Variable | Description |
|----------|-------------|
| LOCKR_API_TOKEN | Your API token for authentication |
| LOCKR_API_URL | Custom API URL (default: production) |
| LOCKR_PROJECT | Default project to use |
License
MIT
