Episode Details

When the same environment variable exists in two places at once, which value does the process actually see? The answer flips depending on where you're standing: on Vercel and n8n, the narrower scope wins — project over team, project over global. On your laptop, dotenv does the opposite, letting your shell silently override the repo's .env file. This episode walks through the documented precedence rules for Vercel Shared Environment Variables, n8n global vs. project variables, Prefect, and dotenv's long-debated override flag — plus the gotchas that cost people days, like Vercel's per-deployment immutability and dotenv's first-vs-last-value inversion depending on a flag you may not remember setting. No universal rule exists. Only per-tool contracts. Key sources: • Vercel — https://vercel.com/docs/environment-variables/shared-environment-variables • Vercel — https://vercel.com/docs/environment-variables • Vercel — https://vercel.com/changelog/share-environment-variables-across-your-team-and-projects Episode 6125 — myweirdprompts.com/n/6125 (permanent short link: myweirdprompts.com/258302)