mcpField
D
Doppler CLI

Doppler CLI

OfficialAgent-ready
docs.doppler.comDeveloper Tools400dopplerUpdated 6d ago
RepositoryVisit website

About Doppler CLI

Doppler CLI retrieves secrets from the Doppler secrets service and injects them into command execution, application startup, and CI/CD workflows. It supports project and configuration selection, streamlining environment variable management across development and deployment stages.

Key features

  1. 01Retrieve secrets from Doppler and inject them into command environments
  2. 02Select different projects and configurations for local development
  3. 03Provide authentication and secret management for CI/CD pipelines

Use cases

  1. 01Securely access API keys and database credentials during local development
  2. 02Automatically inject environment-specific secrets in continuous deployment workflows
  3. 03Manage and switch between different configuration sets across multiple development environments

Install

Pick your OS or package manager and run the command in a terminal.

$
brew install dopplerhq/cli/doppler

Once installed, rundoppler --versionto confirm it works.

Example commands

Common commands in the order you’d use them.

01
doppler login
02
doppler setup
03
doppler run -- npm start

Details

From the project README

Doppler CLI

The Doppler CLI is the official tool for interacting with your Doppler secrets and configuration.

You can:

  • Manage your secrets, projects, and environments
  • Execute applications with your secrets injected into the environment
  • View activity and audit logs

Install

The Doppler CLI is available in several popular package managers. It can also be installed via shell script, GitHub Action, or downloaded as a standalone binary.

For more info, including instructions on verifying binary signatures, see the Install page.

macOS

Using brew is recommended:

$ brew install dopplerhq/cli/doppler
$ doppler --version

To update:

$ brew upgrade doppler

For installation without brew, see the Install page.

Windows

Using winget is recommended:

$ winget install doppler
$ doppler --version

To update:

$ winget upgrade doppler

For additional options, see the Install page.

Shell script

This option is recommend for CI jobs and other environments that won't make use of package manager updates.

$ (curl -Ls --tlsv1.2 --proto "=https" --retry 3 https://cli.doppler.com/install.sh || wget -t 3 -qO- https://cli.doppler.com/install.sh) | sh

For more info, see the Install page.

Linux

See Install page for instructions.

Docker

See Install page for instructions.

GitHub Action

You can install the latest version of the CLI via GitHub Action. See the cli-action repo for more info.

Usage

Setup should only take a minute (literally). You'll authorize the CLI to access your Doppler workplace, and then select your project and config.

$ doppler login                     # generate auth credentials
$ doppler setup                     # select your project and config
# optional
$ doppler configure --all           # view local configuration

By default, doppler login scopes the auth token to the root directory (--scope=/). This means that the token will be accessible to projects using the Doppler CLI in any subdirectory. To limit this, specify the scope flag during login: doppler login --scope=./ or doppler login --scope ~/projects/backend.

Setup (i.e. doppler setup) scopes the selected project and config to the current directory (--scope=./). You can also modify this scope with the scope flag. Run doppler help for more information.

Go Version

This project defines its Go version in a number of places. If updating the Go version, search for GO_VERSION_DEF and ensure that all locations are updated.

Comments

Markdown supported