2020-05-02 21:55:20 +00:00
|
|
|
# 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 :planningpoker, PlanningpokerWeb.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 :planningpoker, PlanningpokerWeb.Endpoint, server: true
|
|
|
|
|
#
|
|
|
|
|
# Then you can assemble a release by calling `mix release`.
|
|
|
|
|
# See `mix help release` for more information.
|
2020-05-04 19:38:02 +00:00
|
|
|
config :planningpoker, PlanningpokerWeb.Endpoint, server: true
|
