Skip to content

Doppler#204

Open
danctila wants to merge 9 commits intomainfrom
danc/doppler
Open

Doppler#204
danctila wants to merge 9 commits intomainfrom
danc/doppler

Conversation

@danctila
Copy link
Contributor

@danctila danctila commented Mar 20, 2026

Description

Migrated environment variable management from .env files to Doppler for centralized secrets management. This eliminates the need to share .env files across the team and provides a web interface for managing secrets across development, testing, and production environments.

See more about Doppler here: https://docs.doppler.com/docs/install-cli

Type of Change

  • Configuration/infrastructure change
  • Documentation update
  • Refactoring (code improvement without changing functionality)

Related Issue(s)

Closes #89

What Changed?

  • Added Doppler CLI integration to backend Makefile (all commands now use doppler run --)
  • Added Doppler CLI integration to web and mobile package.json scripts
  • Created doppler.yaml config files for backend, web, and mobile projects (easier juts for first time setup)
  • Updated CI workflows (WebCI, MobileCI) to install Doppler CLI and use service tokens
  • Removed obsolete db-setup-env Makefile target
  • Updated all READMEs with Doppler setup instructions
  • Added deprecation notices to .env.sample files

Testing & Validation

How this was tested

  1. Verified backend connects to local Supabase using Doppler secrets
  2. Tested web app builds and runs with Doppler (+ connects to backend at /test-api)
  3. Confirmed all make commands work with Doppler integration
  4. Validated CI workflows install Doppler CLI correctly

Unfinished Work & Known Issues

  • None, this PR is complete and production-ready
  • The following items are intentionally deferred:

Pre-Merge Checklist

Code Quality

  • Code follows the project's style guidelines and conventions
  • Self-review completed
  • No debugging code, console logs, or commented-out code left behind
  • No merge conflicts with the base branch
  • Meaningful commit messages that explain the "why"

Testing & CI

  • All CI checks are passing
  • All new and existing tests pass locally
  • Test coverage hasn't decreased
  • Linting passes without errors

Documentation

  • Code is self-documenting or includes helpful comments for complex logic
  • API documentation updated (N/A)
  • Type definitions are accurate and up-to-date (N/A)

@danctila danctila self-assigned this Mar 20, 2026
@codecov
Copy link

codecov bot commented Mar 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 10.23%. Comparing base (15754bf) to head (5217d44).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##             main     #204       +/-   ##
===========================================
- Coverage   84.00%   10.23%   -73.77%     
===========================================
  Files           7       92       +85     
  Lines          50     3195     +3145     
  Branches       24       24               
===========================================
+ Hits           42      327      +285     
- Misses          8     2863     +2855     
- Partials        0        5        +5     
Flag Coverage Δ
backend 23.04% <ø> (?)
mobile 84.00% <ø> (ø)
web 0.71% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 85 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Note:
- This is a workaround for having to adjust the package scripts which run the doppler CLI command
- We don't use secrets in these CI workflows so this is only to have the doppler command available which I think is cleaner than adjusting the package scripts to be the old "non-doppler" commands used for CI and then new commands with doppler be more annoying to type (e.g. "npm run dev:doppler" on every use just so CI can use the base command for no doppler usage)
@danctila danctila marked this pull request as ready for review March 20, 2026 23:16
@danctila danctila requested a review from Dao-Ho March 20, 2026 23:17
"test:coverage": "doppler run -- jest --coverage"
"test": "jest",
"test:watch": "jest --watch",
"test:coverage": "jest --coverage"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ts passes locally with doppler command so idk what happens in CI but this is fine now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: API Key Management

1 participant