Configuration and provider setup
The operator path for configuring CALIBER: ports, database, LLM provider and gateway, object store, workflow storage, and event backend.
Use this page when you need the operator path for configuring CALIBER: core runtime, ports, database, LLM provider choice, object store, workflow storage, and event backend.
At a glance
| Area | Representative settings | Deep reference |
|---|---|---|
| App ports and local bring-up | CALIBER_PORT, MLFLOW_PORT, MLFLOW_GATEWAY_PORT | Local bring-up |
| Metadata database | CALIBER_DATABASE_URL | Platform |
| LLM provider and gateway | CALIBER_LLM_PROVIDER, CALIBER_LLM_BASE_URL | Gateways |
| Object store | CALIBER_OBJECT_STORE_* | Object store |
| Workflow file storage | CALIBER_WORKFLOW_STORAGE_* | Storage and state |
| Event backend | CALIBER_WORKFLOW_RUN_EVENT_BACKEND | Workflows architecture |
1. Configure the core runtime first
Start with the basics that determine whether CALIBER can boot and persist state:
- runtime ports
- metadata database
- object or workflow storage
- event backend
Do not start with optional tuning before these are correct.
2. Configure provider access deliberately
The current repository exposes configurable LLM provider and gateway settings. For local development, the defaults are intentionally safer and smaller than a production deployment.
Use Config and environment reference when you need the representative variable names in one place.
3. Treat secret values as sources, not literals
The configuration surface includes *_SOURCE fields for secret-backed values. That matters because CALIBER resolves secret sources rather than encouraging raw credential literals throughout deployment configuration.
4. Verify after configuration
After any meaningful configuration change, verify:
- the service still boots
- readiness is healthy
- the storage and provider dependencies are reachable
Use: