Skip to content

Configuration Reference

Alloy Host stores its configuration in ~/.alloy-it/config.yaml.

Config file

~/.alloy-it/config.yaml
host:
  vagrant_path: /custom/path/to/vagrant
  vbox_manage_path: /custom/path/to/VBoxManage

By default both paths are auto-discovered from your PATH. Set them only if your tools are installed in a non-standard location.

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 host configuration (nested under host:)
├── vm/vms.yaml          # registered environments (managed automatically)
└── catalog/             # local catalog clone (populated by `catalog update`)

Environment directories are created as <cwd>/<name>/ when you run alloy-host init; they are not stored inside ~/.alloy-it/.

Registry

~/.alloy-it/vm/vms.yaml is managed automatically. It records registered environments. 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:

alloy-host catalog update

The --remote flag is used when cloning the catalog repository for the first time. Updating an existing clone uses the remote already configured in that Git repo—not a new --remote on every catalog update.

Next steps