# Install dynaconf with Homebrew, dnf Configuration Management for Python. Version 3.3.2 via Homebrew; verified 2026-07-01. ## Install ```sh sudo av install brew:dynaconf ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install dynaconf ``` Evidence: local Homebrew formula metadata ### Linux - dnf (92%): ```sh sudo dnf install python3-dynaconf ``` Evidence: Fedora Rawhide package metadata: python3-dynaconf from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst ## Package facts - **Package key:** brew:dynaconf - **Package manager:** Homebrew - **Package manager page:** - **Version:** 3.3.2 - **Source summary:** Configuration Management for Python - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** MIT - **Source archive:** - **Last updated:** 2026-07-01T00:05:42Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - dynaconf (cli) - dynaconf (alias) ## Dependencies - python@3.14 ## Install behavior - Post-install hook: not defined - Bottle: available on all ## Freshness - Page generated: 2026-07-08 - Package-manager version: 3.3.2 - Package-manager updated: 2026-07-01 - Local data: ok - Upstream repository: https://www.dynaconf.com/ - info: Release/tag comparison is only available for GitHub repositories. ## Project history and usage Dynaconf is a Python configuration-management library and CLI for layered settings, environment-variable overrides, validation, and secrets handling across plain Python projects and web frameworks. ### Project history Dynaconf's public package history begins in August 2015, when the 0.1.0 release was uploaded to PyPI and the GitHub repository was created. The README presents it as configuration management for Python, inspired by the 12-factor app approach, with support for multiple file formats, environment overlays, validation, HashiCorp Vault, Redis, Django, Flask, and a CLI. The project grew into a long-lived Python packaging fixture rather than a one-off framework extension. Its documentation and README emphasize generated `settings.toml` and `.secrets.toml` files, environment-variable overrides, and a `dynaconf` executable for init, list, write, validate, and export workflows. ### Adoption history Adoption has come mainly from Python application teams that want one settings layer across local files, environment variables, framework integrations, and secret stores. Its packaging footprint includes PyPI and Homebrew, with the Homebrew formula tracking the 3.x line and PyPI showing active releases through 2026. ### How it is used Typical usage starts with `dynaconf init`, which creates a project settings file and optional secrets file, then application code imports a `Dynaconf` settings object. Users can override configuration with prefixed environment variables and can move secrets to `.secrets.*`, Vault, or Redis. ### Why package nerds care Dynaconf is notable in package-manager culture because it packages a common application concern, configuration layering, as both a library and a CLI. It sits between framework-native settings systems, dotenv loaders, and secret-store clients, making it useful to compare with Pydantic Settings, environs, python-decouple, django-environ, and Hydra. ### Timeline - 2015: GitHub repository is created and Dynaconf 0.1.0 appears on PyPI. - 2020s: Documentation highlights Django, Flask, Vault, Redis, multiple file formats, validation, and CLI workflows. - 2026: PyPI shows active 3.x releases, while Homebrew packages Dynaconf as a CLI-accessible Python tool. ### Related projects - Related projects include Pydantic Settings, python-dotenv, environs, python-decouple, django-environ, Flask configuration, Django settings, HashiCorp Vault, Redis, and the Rust-oriented Hydroconf project linked from the Dynaconf README. ### Sources - - - - - ## Security Notes infrastructure mutation or orchestration signal. - **Geiger risk:** orange / medium - infrastructure mutation or orchestration signal ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: settings.toml, .secrets.toml ## Credential files - Unix: .secrets.toml ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** dynaconf - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - dnf - python3-dynaconf - 3.1.2-21.fc45: normalized package name match | Fedora Rawhide package metadata: python3-dynaconf from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst | A dynamic configurator for python projects | https://github.com/rochacbruno/dynaconf ## Related links - [Secret-risk packages](https://www.automicvault.com/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [python@3.14](https://www.automicvault.com/pkg/brew/python-3-14/) - Runtime dependency declared by Homebrew. - [setconf](https://www.automicvault.com/pkg/brew/setconf/) - Shares av.db curated category or tags: cli, configuration, developer-tools, python, settings. - [envelope](https://www.automicvault.com/pkg/brew/envelope/) - Shares av.db curated category or tags: cli, configuration, developer-tools, environment-variables. - [envio](https://www.automicvault.com/pkg/brew/envio/) - Shares av.db curated category or tags: cli, configuration, developer-tools, environment-variables. - [envv](https://www.automicvault.com/pkg/brew/envv/) - Shares av.db curated category or tags: cli, configuration, developer-tools, environment-variables. - [butane](https://www.automicvault.com/pkg/brew/butane/) - Shares av.db curated category or tags: cli, configuration, developer-tools. - [config-file-validator](https://www.automicvault.com/pkg/brew/config-file-validator/) - Shares av.db curated category or tags: cli, configuration, developer-tools. - [dhall-bash](https://www.automicvault.com/pkg/brew/dhall-bash/) - Shares av.db curated category or tags: cli, configuration, developer-tools. - [dhall-json](https://www.automicvault.com/pkg/brew/dhall-json/) - Shares av.db curated category or tags: cli, configuration, developer-tools. ## Combined YAML source View the package source record on GitHub. [combined/dynaconf.yml](https://github.com/automic-vault/db/blob/main/combined/dynaconf.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph