From 1fea5fd9f7df4330cc426f7a4b41db22bb5fb12a Mon Sep 17 00:00:00 2001
From: Jyri Genral <jyri.genral@protonmail.ch>
Date: Wed, 19 May 2021 21:55:50 +0300
Subject: [PATCH] Configure secrets at runtime in prod release

---
 config/prod.exs                          | 2 +-
 config/{prod.secret.exs => releases.exs} | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)
 rename config/{prod.secret.exs => releases.exs} (93%)

diff --git a/config/prod.exs b/config/prod.exs
index 5486193..359eb97 100644
--- a/config/prod.exs
+++ b/config/prod.exs
@@ -52,4 +52,4 @@ config :logger, level: :info
 
 # Finally import the config/prod.secret.exs which loads secrets
 # and configuration from environment variables.
-import_config "prod.secret.exs"
+# import_config "prod.secret.exs" # removed for using runtime configuration
diff --git a/config/prod.secret.exs b/config/releases.exs
similarity index 93%
rename from config/prod.secret.exs
rename to config/releases.exs
index 11d66d0..30abce4 100644
--- a/config/prod.secret.exs
+++ b/config/releases.exs
@@ -2,7 +2,7 @@
 # from environment variables. You can also hardcode secrets,
 # although such is generally not recommended and you have to
 # remember to add this file to your .gitignore.
-use Mix.Config
+import Config
 
 database_url =
   System.get_env("DATABASE_URL") ||
@@ -35,7 +35,7 @@ config :runosaari, RunosaariWeb.Endpoint,
 # If you are doing OTP releases, you need to instruct Phoenix
 # to start each relevant endpoint:
 #
-#     config :runosaari, RunosaariWeb.Endpoint, server: true
+config :runosaari, RunosaariWeb.Endpoint, server: true
 #
 # Then you can assemble a release by calling `mix release`.
 # See `mix help release` for more information.