From 412acb91d62df65ef5ed711afc6d183d2cb55cb9 Mon Sep 17 00:00:00 2001 From: Andrew Shu Date: Sun, 30 Jun 2024 15:27:13 -0700 Subject: [PATCH] config: migrate to import Config (was use Mix.Config) --- config/config.exs | 31 +------------------------------ 1 file changed, 1 insertion(+), 30 deletions(-) diff --git a/config/config.exs b/config/config.exs index 87d3f59..becde76 100644 --- a/config/config.exs +++ b/config/config.exs @@ -1,30 +1 @@ -# 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 :silent_video, key: :value -# -# And access this configuration in your application as: -# -# Application.get_env(:silent_video, :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" +import Config