From de6814751aaa30aad1b1badea4dce39bfd0d753f Mon Sep 17 00:00:00 2001
From: runephilosof-abtion
 <57357936+runephilosof-abtion@users.noreply.github.com>
Date: Tue, 8 Feb 2022 15:24:32 +0100
Subject: [PATCH] [Config] Suggest avoiding new environments

---
 configuration.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/configuration.rst b/configuration.rst
index f76a2aa09aa..3d93ba7d57d 100644
--- a/configuration.rst
+++ b/configuration.rst
@@ -464,6 +464,10 @@ going to production:
     It's common for environments to be similar to each other, so you can
     use `symbolic links`_ between ``config/packages/<environment-name>/``
     directories to reuse the same configuration.
+    
+    There are benefits to separating configuration from code. So try to avoid
+    creating new environments and instead set environment variables.
+    This way it is easy to add another environment for staging/qa/review applications.
 
 .. _config-env-vars: