### Instalation
```
pip install configus
```
### Features
- [x] Unified spec for process config
- [x] Strict validation of config, no more trailing whitespaces or runtime panics from malphormed uri's
- [x] Support parametrization from env variables and cli arguments at the same time.
- [x] The same param could passed as `export DEBUG=on` or `--debug=on`
- [x] Auto load of `.env` file
- [x] Easy to mock for unit tests
### Usage
Let start with a simple spec that our requires `debug`, `version` and `secret_cookie` configuration params
```python
# app.py
from configus import config, trafaret as t
if __name__ == '__main__':
# Describes shape of the data params which will be taken either from env, cli args or envfile.
schema = t.Dict(DEBUG=t.StrBool, VERSION=t.Float, SECRET_COOKIE=t.String)
env_vars = config(schema=schema)
assert env_vars == {'DEBUG': True, VERSION: 0.1, SECRET_COOKIE=<......>}
```
Once schema defined we can pass variables throw env
```shell
DEBUG=1 VERSION=1.0 SECRET_COOKIE=yo python app.py
```
Cmd flags
```shell
python app.py --debug=1 version=1.0
```
Or even both
```shell
export VERSION=1.0
export SECRET_COOKIE=yo
python app.py --debug=2
```
Metadata
Release files for configus 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| configus-0.1.4.tar.gz | 3.1 kB | Without provenance | Details for configus-0.1.4.tar.gz |
Release files / configus-0.1.4.tar.gz
| Download URL | configus-0.1.4.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc325fd47f7f9ef28ab03fcb35d4f4d26c3b500bb20e6ab206a59b99d6648041
|
|
BLAKE2b-256 checksum How to use checksums |
6bede89d2ae969c22e6ce23359ab339fab40f18dc52a667c218ade758912fceb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for configus 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.