Configuration - iGent Concert

Environment Variables

Variable	Default	Description
`UNISON_LISTEN`	`127.0.0.1:8005` in Fabric PM2, `127.0.0.1:4100` standalone	Listen address (host:port)
`UNISON_VALKEY_URL` / `VALKEY_URL`	`redis://127.0.0.1:6379`	Valkey/Redis-compatible backing store
`UNISON_KEY_PREFIX`	`unison`	Prefix for Valkey keys
`UNISON_API_KEY`	`dev`	Full-access key (used by Diminuendo)
`UNISON_AGENT_API_KEY`	auto-generated	Read-only key (used by Podium agents)
`UNISON_ENCRYPTION_KEY`	unset	Base64 32-byte AES-GCM key for encrypted namespaces

CLI Arguments

All environment variables can be overridden via CLI:

unison \
  --listen=0.0.0.0:4100 \
  --valkey-url=redis://127.0.0.1:6379 \
  --api-key=my-secret \
  --agent-key=agent-secret

Valkey Requirements

Production Unison should use a managed Valkey/Redis-compatible endpoint with TLS for non-loopback deployments, persistence, backups, monitoring, and failover. Local development can reuse a local server or auto-start the Bun-native valkey-bun backend when no explicit URL is configured.

Diminuendo Integration

Diminuendo's AppConfig.ts includes:

UNISON_URL=http://127.0.0.1:8005       class="token comment"># Unison service address
UNISON_API_KEY=dev                     class="token comment"># Shared with Unison
UNISON_AGENT_API_KEY=dev-agent         class="token comment"># Passed to Podium agents via secrets

In the root Fabric stack, Unison is a PM2-managed service. Standalone gateway work should point UNISON_URL and the service keys at an already running Unison process.