# Installer confd avec Homebrew, apk, Nix Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de confd pour les workflows d'agents IA. ## installation ```sh sudo av install brew:confd ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install confd ``` Preuve: local Homebrew formula metadata ### Linux - apk (92%): ```sh sudo apk add confd ``` Preuve: Alpine Linux edge package indexes: confd from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz - Nix (92%): ```sh nix profile install nixpkgs#confd ``` Preuve: nixpkgs package indexes: pkgs/by-name/co/confd/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Faits du paquet - **Clé du paquet:** brew:confd - **Gestionnaire de paquets:** Homebrew - **Version:** 0.16.0 - **Résumé source:** Manage local application configuration files using templates - **Page d'accueil:** - **Dépôt:** - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - confd (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 0.16.0 ## Historique du projet et usages confd is a lightweight configuration-management daemon and CLI for rendering local configuration files from templates backed by service-discovery and key-value systems. It became familiar in early container and microservice deployments because it sat beside an application, watched systems such as etcd or Consul, rendered files, and triggered reload commands. ### Historique du projet The project presents itself as a Go tool for keeping local configuration files up to date from etcd, Consul, DynamoDB, Redis, Vault, ZooKeeper, AWS SSM Parameter Store, environment variables, or files. Its default configuration model centers on TOML at /etc/confd/confd.toml plus template resources under /etc/confd. Release notes show the project expanding alongside the infrastructure systems common in the mid-2010s: DynamoDB support appeared in the v0.10 era, Vault and Redis arrived in 0.12 alpha releases, etcd v3 and Windows support arrived in v0.13.0, and AWS SSM Parameter Store plus file backends arrived in v0.14.0. ### Historique d'adoption confd was adopted mainly as glue for hosts and containers that needed dynamic configuration without pulling a full configuration-management stack into the application. Its official community pointers to IRC, a mailing list, and a project website reflect the period when service discovery and sidecar-style config rendering were still being standardized in operations culture. The Homebrew, apk, and Nix package entries in the supplied package facts reflect its continued packaging as a small operational binary rather than a language library. ### Modes d'utilisation Typical use is to define template resources, point confd at a backend, render target files, and optionally run checks or reload commands when the rendered configuration changes. The tool is especially associated with daemon configuration, reverse proxies, and twelve-factor-ish deployments where authoritative values live outside the local filesystem. ### Pourquoi les passionnés de paquets s'y intéressent For package maintainers, confd is a good example of the mid-2010s Go single-binary ops tool: statically distributable, service-discovery aware, and useful even when installed outside a larger platform. Its formula/cross-platform packaging value comes from turning distributed configuration into a conventional executable with predictable /etc/confd paths. ### Chronologie - 2015: v0.10.0 release notes list DynamoDB backend support and a build-system change to gb. - 2016: 0.12 alpha releases added Vault, DynamoDB, and Redis backend work. - 2017: v0.13.0 added etcd v3 and Windows support; v0.14.0 added AWS SSM Parameter Store and file backends. - 2018: v0.16.0 included backend improvements for etcd v3, Vault, file, and Redis and shipped smaller UPX-compressed executables. ### Related projects - Official documentation names etcd, Consul, DynamoDB, Redis, Vault, ZooKeeper, AWS SSM Parameter Store, and Go templates as core adjacent technologies. ### Sources - - - - - - - ## Notes de sécurité narrow executable package without higher-risk signals. - **Risque Geiger:** vert / faible - narrow executable package without higher-risk signals ## 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: /etc/confd/confd.toml, /etc/confd/conf.d/*.toml, /etc/confd/templates/*.tmpl ## Autres enregistrements de gestionnaires de paquets - Nix - confd: normalized package name match | nixpkgs package indexes: pkgs/by-name/co/confd/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - apk - confd - 0.30.0-r5: normalized package name match | Alpine Linux edge package indexes: confd from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | manage local application configuration files using templates and data from multiple backends | https://github.com/abtreece/confd - apk - confd-doc - 0.30.0-r5: normalized package name match | Alpine Linux edge package indexes: confd-doc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | manage local application configuration files using templates and data from multiple backends (documentation) | https://github.com/abtreece/confd - apk - confd-openrc - 0.30.0-r5: normalized package name match | Alpine Linux edge package indexes: confd-openrc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | manage local application configuration files using templates and data from multiple backends (OpenRC init scripts) | https://github.com/abtreece/confd ## Combined YAML source View the package source record on GitHub. [combined/confd.yml](https://github.com/mxcl/pkgdb/blob/main/combined/confd.yml) ## Sources - 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