From 58bc4959f61ec2a05b492122c7e784bc921b8e88 Mon Sep 17 00:00:00 2001 From: Cory Dransfeldt Date: Sat, 25 Mar 2023 11:18:54 -0700 Subject: [PATCH] (fix) nbsp vs space wrapping issue --- src/posts/2023/env-files-eleventy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/posts/2023/env-files-eleventy.md b/src/posts/2023/env-files-eleventy.md index b3f969bd..59a1d977 100644 --- a/src/posts/2023/env-files-eleventy.md +++ b/src/posts/2023/env-files-eleventy.md @@ -6,7 +6,7 @@ tags: ['.env', '11ty', 'eleventy'] --- **dotenv-flow:** -> **dotenv-flow** extends **dotenv** adding the ability to have multiple `.env*` files like `.env.development`, `.env.test` and `.env.production`, also allowing defined variables to be overwritten individually in the appropriate `.env*.local` file. +> **dotenv-flow** extends **dotenv** adding the ability to have multiple `.env*` files like `.env.development`, `.env.test` and `.env.production`, also allowing defined variables to be overwritten individually in the appropriate `.env*.local` file. The Eleventy docs recommend the `dotenv` package for working with `.env` files[^1], but I've found `dotenv-flow` to be a bit more useful inasmuch as support for `.env*` file patterns make development more convenient.