dynaconf - Configuration Management for Python.
Features
- Inspired by the 12-factor application guide
- Settings management (default values, validation, parsing, templating)
- Protection of sensitive information (passwords/tokens)
- Multiple file formats
toml|yaml|json|ini|pyand also customizable loaders. - Full support for environment variables to override existing settings (dotenv support included).
- Optional layered system for multi environments
[default, development, testing, production] - Built-in support for Hashicorp Vault and Redis as settings and secrets storage.
- Built-in extensions for Django and Flask web frameworks.
- CLI for common operations such as
init, list, write, validate, export. - full docs on https://dynaconf.com
Install
$ pip install dynaconf
Initialize Dynaconf on project root directory
$ cd path/to/your/project/
$ dynaconf init -f toml
⚙️ Configuring your Dynaconf environment
------------------------------------------
🐍 The file `config.py` was generated.
🎛️ settings.toml created to hold your settings.
🔑 .secrets.toml created to hold your secrets.
🙈 the .secrets.* is also included in `.gitignore`
beware to not push your secrets to a public repo.
🎉 Dynaconf is configured! read more on https://dynaconf.com
TIP: You can select
toml|yaml|json|ini|pyondynaconf init -f <fileformat>toml is the default and also the most recommended format for configuration.
Dynaconf init creates the following files
.
├── config.py # This is from where you import your settings object (required)
├── .secrets.toml # This is to hold sensitive data like passwords and tokens (optional)
└── settings.toml # This is to hold your application settings (optional)
On the file config.py Dynaconf init generates the following boilerplate
from dynaconf import Dynaconf
settings = Dynaconf(
envvar_prefix="DYNACONF", # export envvars with `export DYNACONF_FOO=bar`.
settings_files=['settings.yaml', '.secrets.yaml'], # Load files in the given order.
)
TIP: You can create the files yourself instead of using the
initcommand as shown above and you can give any name you want instead of the defaultconfig.py(the file must be in your importable python path) - See more options that you can pass toDynaconfclass initializer on https://dynaconf.com
Using Dynaconf
Put your settings on settings.{toml|yaml|ini|json|py}
username = "admin"
port = 5555
database = {name='mydb', schema='main'}
Put sensitive information on .secrets.{toml|yaml|ini|json|py}
password = "secret123"
IMPORTANT:
dynaconf initcommand puts the.secrets.*in your.gitignoreto avoid it to be exposed on public repos but it is your responsibility to keep it safe in your local environment, also the recommendation for production environments is to use the built-in support for Hashicorp Vault service for password and tokens.
Optionally you can now use environment variables to override values per execution or per environment.
# override `port` from settings.toml file and automatically casts as `int` value.
export DYNACONF_PORT=9900
On your code import the settings object
from path.to.project.config import settings
# Reading the settings
settings.username == "admin" # dot notation with multi nesting support
settings.PORT == 9900 # case insensitive
settings['password'] == "secret123" # dict like access
settings.get("nonexisting", "default value") # Default values just like a dict
settings.databases.name == "mydb" # Nested key traversing
settings['databases.schema'] == "main" # Nested key traversing
More
- Settings Schema Validation
- Custom Settings Loaders
- Vault Services
- Template substitutions
- etc...
There is a lot more you can do, read the docs: http://dynaconf.com
Contribute
Main discussions happens on Discussions Tab learn more about how to get involved on CONTRIBUTING.md guide
More
If you are looking for something similar to Dynaconf to use in your Rust projects: https://github.com/rubik/hydroconf
And a special thanks to Caneco for the logo.
2 maintainers
Metadata
2 maintainers
Release files for dynaconf 3.3.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dynaconf-3.3.5.tar.gz | 333.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dynaconf-3.3.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 604.9 kB
Release files / dynaconf-3.3.5.tar.gz
| Download URL | dynaconf-3.3.5.tar.gz |
|---|---|
| Size | 333.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a08f6ab44025034ef3c9f86b32548ab01efd4039094a74bd9f028a43c63d016f
|
|
BLAKE2b-256 checksum How to use checksums |
71e4723ba469856bb493c948985e5bd562c8a65f2b93e70c896e9764ab76de00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency logRelease files / dynaconf-3.3.5-py3-none-any.whl
| Download URL | dynaconf-3.3.5-py3-none-any.whl |
|---|---|
| Size | 271.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b3b4a753d5c866fc85466b65fc58d4954f6ed7dc8aa67f2b15bcbfd85d184687
|
|
BLAKE2b-256 checksum How to use checksums |
9541b38501c34c40c3261868a2af8ed5fffe3e6d889c680638708de27eb57788
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency log
