Although config by url is an Ecto specific function, parsing values from a postgres url is required in environments where these values do not exist or can change frequently.
If one were to use Ecto -- which does seem to be the go to -- a fully formed repo configuration is available from the Repo in the form of MyApp.Repo.config(), and it seems odd it must be declared again.
It would be beneficial if ecto was present, that the config could pull from the repo.
Although config by url is an Ecto specific function, parsing values from a postgres url is required in environments where these values do not exist or can change frequently.
If one were to use Ecto -- which does seem to be the go to -- a fully formed repo configuration is available from the Repo in the form of
MyApp.Repo.config(), and it seems odd it must be declared again.It would be beneficial if ecto was present, that the config could pull from the repo.