# Monorepo best practices
**URL:** https://community.doppler.com/t/monorepo-best-practices/983
**Category:** Need Help
**Created:** [February 9, 2023, 2:25pm UTC](https://community.doppler.com/t/monorepo-best-practices/983 "2023-02-09T14:25:39Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@btakashi](https://community.doppler.com/u/btakashi)
#### Post date: [February 9, 2023, 2:25pm UTC](https://community.doppler.com/t/monorepo-best-practices/983/1 "2023-02-09T14:25:39Z")
Hi all! I am trying to clean up the environment settings for my Typescript monorepo, it’s unclear to me how best to approach this without introducing a lot of duplication. Some environment variables are shared across one or more packages; other environment variables are specific to a particular package. Should this be modeled as one project, or several? This seems like a common enough problem that someone must have come up with a solution. I would love to use Doppler, it looks great in all other respects but I need to figure this out in order for it to be a viable solution. Any ideas / input appreciated!!
---
### Author:  [@Grraahaam](https://community.doppler.com/u/Grraahaam)
#### Post date: [April 18, 2023, 10:12am UTC](https://community.doppler.com/t/monorepo-best-practices/983/2 "2023-04-18T10:12:26Z")
Hi @btakashi !
You could reference secrets from a global vault project for example, if you want to avoid duplication and be able to change once and apply everywhere automatically ✌
About monorepo best practices, here’s a thread about it :
- [Multi-project Doppler Setup - #2 by Grraahaam](https://community.doppler.com/t/multi-project-doppler-setup/1088/2)
Example configuration :
```yaml
# doppler.yaml
setup:
- project: frontend
config: dev
path: frontend/
- project: backend
config: dev
path: backend/
```