Configuration is just another API of your app. It allows us to preset or modify it’s behavior based on where it is installed and how it will be executed, providing more flexibility to the users of such software.
It is important to provide a clear separation of configuration and code. This is because config varies substantially across deploys and executions, code should not. The same code can be run inside a container or in a regular machine, it can be executed in production or in testing environments.
Configuration management is an important aspect of the architecture of any system. But it is sometimes overlooked.
Classyconf is here to help, it’s the configuration management solution for perfectionists with deadlines.
- What’s classyconf
- Getting started
- Configuration Loaders
- Why not use environment variables directly?
- When should I use configuration files?
- Why are executable config files a bad idea?
- Is classyconf tied to Django or Flask?
- Why create a library similar to prettyconf or goodconf instead of using it?
- How does classyconf compare to python-dotenv?
- What are some useful third-parties casts for Django?