Configuration Reference¶
Alloy Host stores its configuration in ~/.alloy-it/config.yaml.
Config file¶
vagrant_path: /custom/path/to/vagrant
vbox_manage_path: /custom/path/to/VBoxManage
By default both are auto-discovered from your PATH. Set them only if your tools are installed in a non-standard location.
Use the CLI to manage these values:
alloy-host config show
alloy-host config set vagrant-path /usr/local/bin/vagrant
alloy-host config set vbox-manage-path /usr/local/bin/VBoxManage
alloy-host config unset vagrant-path
File layout¶
~/.alloy-it/
├── config.yaml # global configuration
├── registry.json # registered environments (managed automatically)
└── catalog/ # local catalog clone (populated by `catalog update`)
Environment directories are created wherever you ran alloy-host init; they are not stored inside ~/.alloy-it/.
Registry¶
~/.alloy-it/registry.json is managed automatically. It records the name, path, blueprint, backend type, and creation time of every environment you've initialized. alloy-host list reads from it.
Do not edit this file manually.
Catalog location¶
The local catalog is stored at ~/.alloy-it/catalog/ as a Git repository. Update it with:
To use a private or internal catalog, pass a custom remote:
Telemetry¶
Alloy Host supports OpenTelemetry tracing. To send traces to a collector, set the standard OTEL environment variable before running any command: