Move runtime configuration from to Vapor or remove it entirely
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Vapor (see env.ex) brings some advantages (it allows functions and loading from files like .env.dev automatically) but right now, we have 1 application configuration being done in Vapor using env.ex and the rest in runtime.exs. We shouldn't ask contributors to learning two different ways of doing runtime config, nor should we do such critical configuration in two different places. We should either migrate all runtime configuration to Vapor (probably this) or remove Vapor and continue with our runtime.exs approach.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the application configuration in env.ex with the remaining runtime configuration in runtime.exs. Decide whether all runtime configuration should move to Vapor or whether Vapor should be removed, then verify that the chosen approach covers the existing configuration consistently without asking contributors to use two systems.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100