Engine Config

Comparable to: Infrastructure as code, Docker Compose configs

Key Concepts

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

• iii-config.yaml defines the engine port, modules, workers, adapters, and queue configs
• Environment variables use ${VAR:default} syntax (default is optional)
• Modules are the building blocks — each enables a capability (API, state, queue, cron, etc.)
• Workers are external binary modules managed via iii.toml and the iii worker CLI commands
• Adapters swap storage backends per module: in_memory, file_based, Redis, RabbitMQ
• Queue configs control retry count, concurrency, ordering, and backoff per named queue
• The engine listens on port 49134 (WebSocket) for SDK/worker connections

Architecture

The iii-config.yaml file is loaded by the iii engine binary at startup. Modules are initialized in order, adapters connect to their backends, and the engine begins accepting worker connections over WebSocket on port 49134. External workers defined in the workers section are spawned as child processes automatically.