Engine Config

Comparable to: infrastructure as code, worker manifests, runtime policy config

Key Concepts

Use the concepts below when they fit the task. Not every deployment needs all workers or adapters.

config.yaml / iii-config.yaml defines engine workers, modules, adapters, ports, observability, RBAC, and worker manager listeners
Environment variables use ${VAR:default} syntax (default is optional)
Workers are the building blocks — each enables a capability (API, state, queue, cron, etc.)
Managed workers are registry, binary, OCI image, or local workers controlled by the worker manager and iii worker CLI
Adapters swap storage and messaging backends: file/KV, Redis, RabbitMQ, local/in-memory where supported
Queue configs control retry count, concurrency, ordering, and backoff per named queue
The engine's private worker WebSocket commonly listens on port 49134
The console commonly runs on 3113, HTTP on 3111, stream WebSocket on 3112, and Prometheus on 9464 when enabled