Packages

Arke project generator. Provides a `mix arke.new` task to bootstrap a new Elixir application with Arke dependencies.

Current section

Files

Jump to
arke_new templates arke_single config dev.exs
Raw

templates/arke_single/config/dev.exs

# For development, we disable any cache and enable
# debugging and code reloading.
#
# The watchers configuration can be used to run external
# watchers to your application. For example, we can use it
# to bundle .js and .css sources.
import Config
config :<%= @arke_app_name %>, <%= @endpoint_module %>,
# Binding to loopback ipv4 address prevents access from other machines.
# Change to `ip: {0, 0, 0, 0}` to allow access from other machines.
http: [ip: {127, 0, 0, 1}, port: 4000],
check_origin: false,
code_reloader: true,
debug_errors: true,
secret_key_base: "<%= @secret_key_base_dev %>",
watchers: []
# ## SSL Support
#
# In order to use HTTPS in development, a self-signed
# certificate can be generated by running the following
# Mix task:
#
# mix phx.gen.cert
#
# Run `mix help phx.gen.cert` for more information.
#
# The `http:` config above can be replaced with:
#
# https: [
# port: 4001,
# cipher_suite: :strong,
# keyfile: "priv/cert/selfsigned_key.pem",
# certfile: "priv/cert/selfsigned.pem"
# ],
#
# If desired, both `http:` and `https:` keys can be
# configured to run both http and https servers on
# different ports.
# Do not include metadata nor timestamps in development logs
config :logger, :console, format: "[$level] $message\n"
config :<%= @arke_app_name %>, dev_routes: true
config :phoenix, :stacktrace_depth, 20
config :phoenix, :plug_init_mode, :runtime
# Guardian configuration
config :arke_auth, ArkeAuth.Guardian,
issuer: "arke_auth",
verify_issuer: true,
token_ttl: %{"access" => {7, :days}, "refresh" => {30, :days}},
secret_key: "<%= @secret_key_base_dev %>"