Where Does Asbru Connection Manager Store Config?
Asbru keeps connections in asbru.yml under .config/asbru with a freeze cache beside it. Linux paths and migration.
Last updated
Asbru stores connections in one YAML file. The live file is asbru.yml inside ~/.config/asbru, with a companion freeze cache that loads first on start. Hand edits to the YAML need the cache deleted afterwards, or the old copy wins.
The project renamed from PAC Manager in version 6, and upgrades copy the old tree aside rather than deleting it. Tabby and mRemoteNG users should note this is a different app with its own format: none of their files import by copying paths. A custom location flag exists for portable layouts.
Where Asbru Connection Manager stores this, by platform
~/.config/asbru/asbru.yml
Connections plus options in one YAML. Companion asbru.nfreeze cache beside it loads first: delete after hand edits. Custom scripts in the scripts subfolder. Override the dir with asbru-cm --config-dir. Legacy ~/.config/pac/pac.yml auto-copies to pac.old on upgrade.
Frequently asked questions
How do I back up Asbru connections?
Copy asbru.yml from ~/.config/asbru with the app closed. The freeze cache and scripts folder travel with it for a full restore. Keep the YAML in a dotfiles repo and ignore the cache, which regenerates.
Why did my hand edits to asbru.yml vanish?
The nfreeze cache loads first and overwrites them. Quit Asbru, edit the YAML, delete asbru.nfreeze, then relaunch. The app rebuilds the cache from your edited file on the next start.
Where is the old PAC Manager config?
At ~/.config/pac/pac.yml from before the 6.x rename. Upgrades copy it to pac.old automatically. Migrate by letting the app import it once, then confirm asbru.yml holds every connection before deleting the fossil.
Notice an outdated path? Let us know.