Chapter 7 — Configuration
Configuring IRIS™ (~/.iris/)
IRIS keeps hand-editable TOML settings under ~/.iris/. A missing file uses
defaults; you do not need to create all files before starting. Keep
credential-bearing configuration private and out of source control.
| File | Purpose |
|---|---|
iris-bench.cfg |
Bench launch preferences, port, log settings, and remembered folder-tree selections. |
iris-tracker.cfg |
Host-wide tracker preferences. Per-run live commands use the run's iris.cmd file. |
iris-butler.cfg |
Butler defaults; a run's iris.cfg can override its global settings. |
derived_metrics.toml |
Saved expressions for the User tab's Derived section. |
config.toml |
Settings shared by the tools, including a license-server override for a private/staging deployment. |
Example Bench preference:
[server]
port = 8765
Precedence: which source wins
The normal precedence is built-in defaults, then the tool's configuration file, then supported environment overrides, then CLI flags or constructor arguments. Later settings override earlier ones. The exact supported keys are version-specific; do not add a key just because a different program uses it.
The Bench's --no-open flag can suppress automatic browser opening; it
does not reverse an open_browser = false preference back to true. The
tracker's debug=True similarly forces verbosity upward; debug=False
does not override a more verbose environment or file preference.
A malformed file is different from a missing file. Tracker configuration errors can prevent startup rather than silently using defaults. Read the named file and error, correct the value or remove the unintended setting, and retry. See Chapter 24 for reference.
Browse and switch runs
In IRIS bundles & benches, the triangle opens a folder; the folder icon selects which runs appear in the list. Opening and selecting are separate. Switch here changes the run shown in the existing Bench, while Start opens a separate Bench for the selected run. The folder tree remembers its state, so you normally do not need to hand-edit its keys.
Network access is a separate responsibility
The Bench has no password. Anyone who can reach its port can view it.
Changing anything, including tracker commands, notes, restarting, or switching
runs, requires localhost on the Bench machine or a supported SSH port-forward
as your own login account. See Chapter 10 for the connection
requirements. Network policy controls viewing access. Use a trusted, encrypted path for
remote viewing; see Chapter 14.
