From 0e71ac4145b159ba87439494f86ebc4b84db56d0 Mon Sep 17 00:00:00 2001
From: Adam Piontek <adam@73k.us>
Date: Mon, 5 Apr 2021 23:08:02 -0400
Subject: [PATCH] remove prod.secret.exs from git tracking

---
 config/prod.secret.exs | 29 -----------------------------
 1 file changed, 29 deletions(-)
 delete mode 100644 config/prod.secret.exs

diff --git a/config/prod.secret.exs b/config/prod.secret.exs
deleted file mode 100644
index c343e6d..0000000
--- a/config/prod.secret.exs
+++ /dev/null
@@ -1,29 +0,0 @@
-# In this file, we load production configuration and secrets
-# 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
-
-secret_key_base =
-  System.get_env("SECRET_KEY_BASE") ||
-    raise """
-    environment variable SECRET_KEY_BASE is missing.
-    You can generate one by calling: mix phx.gen.secret
-    """
-
-config :home73k, Home73kWeb.Endpoint,
-  http: [
-    port: String.to_integer(System.get_env("PORT") || "4000"),
-    transport_options: [socket_opts: [:inet6]]
-  ],
-  secret_key_base: secret_key_base
-
-# ## Using releases (Elixir v1.9+)
-#
-# If you are doing OTP releases, you need to instruct Phoenix
-# to start each relevant endpoint:
-#
-#     config :home73k, Home73kWeb.Endpoint, server: true
-#
-# Then you can assemble a release by calling `mix release`.
-# See `mix help release` for more information.