This guide will show you how to create and use Doppler projects for scoping secrets to different applications.
A project in Doppler is where you define the app config and secrets for a single service or application.
Every new Doppler workplace comes with a default first-project but you create a new project by clicking the + button.
A project needs a name and an optional description. We recommend the name be hyphen-separated and all lowercase.
Each project has three default environments for defining configuration at the root level: Development, Staging, and Production. Configs are responsible for vaulting and managing app config and secrets such as API keys, database urls, certs, etc...
Each environment may optionally have branch configs, which allow overrides from the root config for that environment. Developers may use this locally to customize their environment, or it could be used in staging and production to support different cloud providers. Learn more in our config branching.
Custom environments can also be created, the most common of which is for CI / CD systems. The order in which the environments appear can also be altered via drag-and-drop.
You can pre-configure the Doppler project and config to use for local development by creating a
doppler.yaml file, either in the root of the repository, or in each app folder if using a monorepo.
You can specify just the project, or the project and config, but we recommend setting both to make setup as easy as possible.
Here's an example:
setup: project: rocket config: dev
Now you'll get an enhanced experience when running
Updated about a month ago