# dynaconf mit Homebrew, dnf installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für dynaconf in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:dynaconf
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install dynaconf
```

  Evidenz: local Homebrew formula metadata

### Linux

- dnf (92%):

```sh
sudo dnf install python3-dynaconf
```

  Evidenz: Fedora Rawhide package metadata: python3-dynaconf from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst

## Paketfakten

- **Paketschlüssel:** brew:dynaconf
- **Paketmanager:** Homebrew
- **Version:** 3.3.4
- **Quellzusammenfassung:** Configuration Management for Python
- **Homepage:** <https://www.dynaconf.com/>
- **Zuletzt aktualisiert:** 2026-07-30T09:07:57Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- dynaconf (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 3.3.4
## Projektgeschichte und Nutzung

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.

### Projektgeschichte

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.

### Adoptionsgeschichte

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.

### Wie es verwendet wird

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.

### Warum Paket-Nerds sich dafür interessieren

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.

### Zeitleiste

- 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.

### Quellen

- <https://github.com/dynaconf/dynaconf#readme>
- <https://api.github.com/repos/dynaconf/dynaconf>
- <https://pypi.org/pypi/dynaconf/json>
- <https://www.dynaconf.com/>
- <https://formulae.brew.sh/formula/dynaconf>


## Sicherheitshinweise

infrastructure mutation or orchestration signal.

- **Geiger-Risiko:** orange / mittel
- 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
## Andere Paketmanager-Einträge

- dnf - python3-dynaconf - 3.2.13-3.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/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | A dynamic configuration system for Python projects | https://github.com/dynaconf/dynaconf


## Combined YAML source

View the package source record on GitHub. [combined/dynaconf.yml](https://github.com/mxcl/pkgdb/blob/main/combined/dynaconf.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph