From 599e5594c2e43a67a01d48bd4c8c1fc05b93e17c Mon Sep 17 00:00:00 2001
From: Ernesto Rico Schmidt <ernesto@helsinki.at>
Date: Wed, 15 Dec 2021 15:53:00 -0400
Subject: [PATCH] Minor tweaks to match the settings

---
 .env.example | 21 +++++++--------------
 1 file changed, 7 insertions(+), 14 deletions(-)

diff --git a/.env.example b/.env.example
index 8384876b..d90e8b70 100644
--- a/.env.example
+++ b/.env.example
@@ -23,16 +23,16 @@ SECRET_KEY=put-something-awesomely-random-here
 # if you use a dev environment where django is not running inside a docker
 # container, but you use the postgres container for the db and map its port,
 # then use localhost as the database hostname
-# (default host: steering-postgres ; or if RUN_IN_DOCKER is False: localhost)
+# (default host: postgres)
 # (default port: 5432)
 # (default name: steering)
 # (default user: steering)
-# (pass is a mandatory setting)
-#DBHOST=
-#DBPORT=
-#DBNAME=
-#DBUSER=
-DBPASS=change-to-something-secure
+# (password is a mandatory setting)
+#DATABASE_HOST=
+#DATABASE_PORT=
+#POSTGRES_DB=
+#POSTGRES_USER=
+POSTGRES_PASSWORD=change-to-something-secure
 
 # The timezone of this server. For a list of all available tz database names see
 # https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
@@ -44,13 +44,6 @@ DBPASS=change-to-something-secure
 # (default: de)
 #LANGUAGE_CODE=
 
-# If steering is run inside a docker container. This will be de default for a
-# production deployment. In a dev scenario you might still want to have the
-# database in its container, but run the steering dev server directly on your
-# host. In this case make this False.
-# (default: True)
-#RUN_IN_DOCKER=
-
 # This should be turned on only for your development environment unless you
 # know exactly what you are doing and what the consequences are.
 # (default: False)
-- 
GitLab