folklore-config
The Folklore framework configuration manager.
Configs are in yaml format stored in app.yaml by default. An environment vairable FOLKLORE_APP_CONFIG_PATH can be used to change the path of the yaml file.
To set current running environment of the app use environment vairable FOLKLORE_ENV. The default env is dev.
Usage
For the given config files:
# app.yaml
app_name: echo
app: echo:service
settings: settings
# settings.py
DB_DSN = 'psycopg2+postgresql://root:123@localhost:5432/dev'
>>> # With this environment vairable set:
>>> # FOLKLORE_ENV=prod
>>>
>>> from folklore_config import config
>>> print(config.env)
'prod'
>>> print(config.app_name)
'echo'
>>> config.settings.update({'TEST': True, 'HELLO': 'world'})
>>> print(config.settings['TEST'])
True
>>> print(config.settings['DB_DSN'])
'psycopg2+postgresql://root:123@localhost:5432/dev'
Metadata
Release files for folklore-config 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| folklore_config-0.2.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for folklore_config-0.2.0-py2.py3-none-any.whl |
Release files / folklore_config-0.2.0-py2.py3-none-any.whl
| Download URL | folklore_config-0.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 5.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
430e93d03d7fb6ef2985d45ac4b3c3e0daf78525a39aad7fede2ac0cd07ef8ae
|
|
BLAKE2b-256 checksum How to use checksums |
6efbecb5ea8f2c7564503cff0e3c7fd111eb10603d72a524a3650cda09c4c3bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.7.4
|
Security for folklore-config 0.2.0
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.