Doppler Setup

Centralize secrets management for your Meridian deployment with Doppler. Sync environment variables across Vercel, local dev, and CI in one place.

Prerequisites

A Doppler account with a project created
Meridian source cloned locally
Vercel CLI installed and authenticated

Step 1 — Create Doppler Configs

Inside your Doppler project, create three environments: dev, staging, and prd. Populate each with the secrets Meridian expects:

DATABASE_URL=postgresql://...
NIMBUS_LICENSE_KEY=...
UPSTASH_REDIS_REST_URL=...
UPSTASH_REDIS_REST_TOKEN=...
SELLAUTH_API_KEY=...
KEYAUTH_OWNER_ID=...
ED25519_PUBLIC_KEY=...

Step 2 — Install Doppler CLI

Follow the official Doppler CLI install guide for your OS. Once installed, authenticate:

doppler login

Step 3 — Link Meridian to Doppler

From the Meridian project root, run setup to select your Doppler project and config:

doppler setup

Choose the dev config for local work. Doppler writes a service token to .env — add it to .gitignore.

Step 4 — Run with Doppler

Prefix any command with doppler run to inject secrets:

doppler run -- npm run dev

Step 5 — Vercel Integration

Install the Doppler Vercel integration from the Doppler dashboard. Map each Vercel environment (Preview, Production) to the matching Doppler config. Secrets sync automatically on every deploy — no manual vercel env add needed.

Need help? Join the Meridian Discord for real-time support from the team.