Configure secrets at runtime in prod release
This commit is contained in:
@@ -52,4 +52,4 @@ config :logger, level: :info
|
|||||||
|
|
||||||
# Finally import the config/prod.secret.exs which loads secrets
|
# Finally import the config/prod.secret.exs which loads secrets
|
||||||
# and configuration from environment variables.
|
# and configuration from environment variables.
|
||||||
import_config "prod.secret.exs"
|
# import_config "prod.secret.exs" # removed for using runtime configuration
|
||||||
|
|||||||
@@ -2,7 +2,7 @@
|
|||||||
# from environment variables. You can also hardcode secrets,
|
# from environment variables. You can also hardcode secrets,
|
||||||
# although such is generally not recommended and you have to
|
# although such is generally not recommended and you have to
|
||||||
# remember to add this file to your .gitignore.
|
# remember to add this file to your .gitignore.
|
||||||
use Mix.Config
|
import Config
|
||||||
|
|
||||||
database_url =
|
database_url =
|
||||||
System.get_env("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
|
# If you are doing OTP releases, you need to instruct Phoenix
|
||||||
# to start each relevant endpoint:
|
# 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`.
|
# Then you can assemble a release by calling `mix release`.
|
||||||
# See `mix help release` for more information.
|
# See `mix help release` for more information.
|
||||||
Reference in New Issue
Block a user