Use dynaconf for settings management
Open
Nobody has claimed this yet.
refactor
- Dominant language
- HTML
- Stars
- 2
- Forks
- 17
- Avg merge
- 7d 18h
- Merged PRs (30d)
- 3
Description
The configuration management started to grow and its really messy.
Switching to dynaconf should:
- make it easier to manage config overrides inside the application
- enable future support for persistent user-config
Also, I wanna leverage Schema type hint support when it gets merged.
Contributor guide
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 mapping the existing configuration management and comparing it with dynaconf's configuration override and persistent user-config capabilities. Check the linked schema type hint dependency before defining the migration scope; done means the application uses dynaconf consistently and the stated configuration goals are supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100