I'm not sure if this is a good idea or not, so not creating a PR for the docs yet (happy to if you like).
To avoid maintaining multiple copies of the .env.local file in development, I just symlinked from a copy in the root of the project to apps/app/.env.local, apps/api/.env.local, apps/web/.env.local and packages/database/.env.
Much better from a workflow standpoint. Any reason not to do this?
I'm not sure if this is a good idea or not, so not creating a PR for the docs yet (happy to if you like).
To avoid maintaining multiple copies of the
.env.local
file in development, I just symlinked from a copy in the root of the project toapps/app/.env.local
,apps/api/.env.local
,apps/web/.env.local
andpackages/database/.env
.Much better from a workflow standpoint. Any reason not to do this?