chore: Migrate from Mix.Config to Config

Author: rogerpinho

config/config.exs

@@ -5,7 +5,7 @@
 # is restricted to this project.
 
 # General application configuration
-use Mix.Config
+import Config
 
 config :brasil_em_dados,
   ecto_repos: [BrasilEmDados.Repo]

config/dev.exs

@@ -1,4 +1,4 @@
-use Mix.Config
+import  Config
 
 # Configure your database
 config :brasil_em_dados, BrasilEmDados.Repo,

config/prod.exs

@@ -1,4 +1,4 @@
-use Mix.Config
+import Config
 
 # For production, don't forget to configure the url host
 # to something meaningful, Phoenix uses this information
@@ -10,7 +10,7 @@ use Mix.Config
 # which you should run after static files are built and
 # before starting your production server.
 config :brasil_em_dados, BrasilEmDadosWeb.Endpoint,
-  url: [host: "example.com", port: 80],
+  url: [host: "brasilemdados.com", port: 80],
   cache_static_manifest: "priv/static/cache_manifest.json"
 
 # Do not print debug messages in production

config/prod.secret.exs

@@ -2,7 +2,7 @@
 # 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
+import Config
 
 database_url =
   System.get_env("DATABASE_URL") ||
@@ -35,7 +35,7 @@ config :brasil_em_dados, BrasilEmDadosWeb.Endpoint,
 # If you are doing OTP releases, you need to instruct Phoenix
 # to start each relevant endpoint:
 #
-#     config :brasil_em_dados, BrasilEmDadosWeb.Endpoint, server: true
+config :brasil_em_dados, BrasilEmDadosWeb.Endpoint, server: true
 #
 # Then you can assemble a release by calling `mix release`.
 # See `mix help release` for more information.

config/test.exs

@@ -1,4 +1,4 @@
-use Mix.Config
+import Config
 
 # Only in tests, remove the complexity from the password hashing algorithm
 config :bcrypt_elixir, :log_rounds, 1