From cad149156ee46ec9feb4929dc1ed5d60a4f4f44e Mon Sep 17 00:00:00 2001 From: Tiago Freire Date: Fri, 22 Jul 2016 09:18:21 -0300 Subject: [WIP] Init. --- config/config.exs | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 config/config.exs (limited to 'config') diff --git a/config/config.exs b/config/config.exs new file mode 100644 index 0000000..2272984 --- /dev/null +++ b/config/config.exs @@ -0,0 +1,30 @@ +# This file is responsible for configuring your application +# and its dependencies with the aid of the Mix.Config module. +use Mix.Config + +# This configuration is loaded before any dependency and is restricted +# to this project. If another project depends on this project, this +# file won't be loaded nor affect the parent project. For this reason, +# if you want to provide default values for your application for +# 3rd-party users, it should be done in your "mix.exs" file. + +# You can configure for your application as: +# +# config :powerdnsx, key: :value +# +# And access this configuration in your application as: +# +# Application.get_env(:powerdnsx, :key) +# +# Or configure a 3rd-party app: +# +# config :logger, level: :info +# + +# It is also possible to import configuration files, relative to this +# directory. For example, you can emulate configuration per environment +# by uncommenting the line below and defining dev.exs, test.exs and such. +# Configuration from the imported file will override the ones defined +# here (which is why it is important to import them last). +# +# import_config "#{Mix.env}.exs" -- cgit v1.2.3