From f821348f090329f84f0f385a2d128b8350f78f50 Mon Sep 17 00:00:00 2001 From: Brendan Irvine-Broque Date: Fri, 8 Aug 2025 16:10:21 -0700 Subject: [PATCH] Clarify environments Using capitalizeed "Cloudflare Environments" is a bit confusing since it's not a named product --- .../changelog/workers/2025-08-08-dot-env-in-local-dev.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/content/changelog/workers/2025-08-08-dot-env-in-local-dev.mdx b/src/content/changelog/workers/2025-08-08-dot-env-in-local-dev.mdx index cc1bc651f059748..298fabc11678c4c 100644 --- a/src/content/changelog/workers/2025-08-08-dot-env-in-local-dev.mdx +++ b/src/content/changelog/workers/2025-08-08-dot-env-in-local-dev.mdx @@ -37,9 +37,7 @@ export default { ## Multiple environments with `.env` files -You may be using [Cloudflare Environments](/workers/wrangler/environments/) to deploy different versions of a Worker with distinct environment variables. For instance, you may have a production and staging environment. - -To set different environment variables for each Cloudflare Environment, create files named `.env.`. +If your Worker defines multiple [environments](/workers/wrangler/environments/), you can set different variables for each environment (ex: production or staging) by creating files named `.env.`. When you use `wrangler --env ` or `CLOUDFLARE_ENV= vite dev`, the corresponding environment-specific file will also be loaded and merged with the `.env` file.