Magiccfg 1.3 Review

~/.config/magiccfg/ ├── config.yaml ├── templates/ │ └── gitconfig.tmpl └── secrets/ └── github-token.age

$ magiccfg apply --fix Checking 14 resources... [WARN] ~/.zshrc: expected mode 644, found 600 → fixed [WARN] ~/.config/nvim/init.lua: missing → restored from catalog [OK] All resources match intended state. Integrate encrypted secrets directly into your config catalog using age (modern, simple encryption). Magiccfg 1.3 transparently decrypts files matching *.age when run with the private key available via $MAGICCFG_AGE_KEY or an age agent. magiccfg 1.3

Example plugin manifest ( plugins/docker-volume/manifest.yaml ): Magiccfg 1

The maintainers of are pleased to announce the release of version 1.3, a significant update to the cross-platform, templated configuration management tool. Magiccfg bridges the gap between simple dotfile managers and heavyweight orchestration tools like Ansible or Puppet, focusing on reproducible, human-readable configuration state across Linux, macOS, and Windows (via WSL and native PowerShell). Example output: Version 1

Example output:

Version 1.3 introduces declarative drift correction, native age encryption support, and a plugin API for custom resource types. 1. Declarative drift detection & auto-repair ( magiccfg apply --fix ) Magiccfg now compares the intended state (your config catalog) against the actual system state. If a file is missing, a symlink is broken, or a permission changes, magiccfg apply --fix will restore intent without re-running every task.

If you used magiccfg verify in scripts, replace it with magiccfg apply --dry-run . Inline shell commands in resources are now deprecated – see Migration Guide for the new plugin-based approach. Example: Using magiccfg 1.3 to manage a developer workstation Catalog structure: