hauleth
Move some configurations in the generated files
Currently Phoenix generates configuration for Ecto in the config/config.exs (I mean option :ecto_repos). Why there? Instead of polluting config.exs (and by extension sys.config) with needless configuration options I believe it would be better to use application env instead. For these unaware of this feature, you can specify “global” configuration within application/0 callback in Mix.Project, ex.:
defmodule MyProject.Mixfile do
use Mix.Project
# …
def application do
[
mod: {MyProject.Application, []},
extra_applications: [:logger],
env: [
ecto_repos: [MyProject.Repo]
]
]
end
# …
end
This will keep only runtime configuration (this option is used almost exclusively in development and testing) in config/config.exs and will not pollute sys.config in the result.
Trending in Discussions
Other Trending Topics
Latest Phoenix Threads
Chat & Discussions>Discussions
Latest on Elixir Forum
Sponsor Spotlight
Develop your skills with books, videos, and courses.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First Post!
dimitarvp
I would love it if we could do that for every dependency!
We can also have mini functions like this:
It would be damn beautiful.
Most Liked
hauleth
The reason is that after some time I come to liking
sys.configand in my deployments I could use this directly instead of using additional tools like config providers. But it become troublesome when this file grows larger and larger for no apparent reason.What I mean is exactly that - have one config file, but keep only runtime configuration there. How often you edit
:ecto_repos? This is configuration option needed only formix ecto.*tasks and is used by anything else, so why the hell it is inconfig/config.exsat all? This option do not configure my application in any way, only tooling, and to be exact - mostly development tooling, as often you do not havemixin production.And that is what I am trying to achieve there - hide unneeded entries from users and keep configuration files as simple and short as possible, do not bloat them with compile time and tooling configuration that has nothing to do with my application behaviour.