Configuration — v0.9.7
Installation scopes, configuration inspection, and migration for Alloy Edge v0.9.7
Start with Track Folder v0.9.7.
alloy-edge link creates the configuration and persists the device credential;
most installations do not need hand-edited YAML.
Installation files
| File | Purpose |
|---|---|
edge-manager.yaml | Backend connection, local or remote process ownership, and supervision |
edge-sync.yaml | Upload, cleanup, lifecycle, and optional pipeline settings |
shared/track_folder under the state directory | Canonical absolute path to the recordings folder |
| Transform YAML | Optional rules for transforming recordings before upload |
| Scope | Configuration | State |
|---|---|---|
| User | $XDG_CONFIG_HOME/alloy-edge or ~/.config/alloy-edge | $XDG_STATE_HOME/alloy-edge or ~/.local/state/alloy-edge |
| Folder-local | <track-folder>/.alloy | <track-folder>/.alloy/state |
| System | /etc/alloy-edge | /var/lib/alloy-edge |
Use --user, --system, or --local to select an installation explicitly.
Without one, the CLI looks for the nearest valid folder-local installation,
then the user installation, then the system installation. A malformed local
installation is an error.
Inspect and validate
alloy-edge config show
alloy-edge config show --json --schema
alloy-edge config checkconfig show prints the authored manager and each referenced sync or transform
file. Add manager or a configured process name to narrow it. The JSON schema
is the complete reference for the version installed on your device; it includes
validation rules and field descriptions. config check validates every
referenced file without starting the runtime.
In v0.9.7, the tracked folder is not an input_dir field in
edge-sync.yaml. Change it with:
alloy-edge config set track-folder /data/recordingsRestart Alloy Edge after changing the tracked folder. Other advanced process
settings require editing their YAML and running alloy-edge config check;
config set does not accept arbitrary manager or sync field addresses.
Migrating an existing installation
An older installation may still store input_dir in edge-sync.yaml. Stop
Alloy Edge and migrate that value to shared/track_folder before starting
v0.9.7. Use the same scope as the linked installation:
alloy-edge config --user migrate-track-folder
alloy-edge config --user checkThe migration preserves the other YAML fields and comments. It is safe to rerun after an interruption. Restart Alloy Edge afterward. Keep the state directory: it contains the persisted device key and is not a disposable cache.
New installations own their process configuration locally. Operators who
want Alloy Cloud to own DeviceState can explicitly enable it with
alloy-edge config --user enable-remote, then restart. This is separate from
the user, system, or folder-local installation scope.