Configuration

cdktr uses an environment-based configuration system. You can set configuration options via environment variables, a .env file, or in some cases command-line arguments. All configuration options can be listed using:

cdktr config list

Configuration Options

Environment VariableDescriptionDefault Value
CDKTR_LOG_LEVELDefault log levelINFO
CDKTR_AGENT_MAX_CONCURRENCYMaximum number of concurrent workflows an agent can handle5
CDKTR_RETRY_ATTEMPTSNumber of times to re-attempt a ZMQ request20
CDKTR_DEFAULT_ZMQ_TIMEOUT_MSDefault timeout for a ZMQ request (milliseconds)3000
CDKTR_PRINCIPAL_HOSTHostname of the principal instance0.0.0.0
CDKTR_PRINCIPAL_PORTDefault port of the principal instance5561
CDKTR_LOGS_LISTENING_PORTListening port for the principal log manager5562
CDKTR_LOGS_PUBLISHING_PORTPublishing port for the principal log manager5563
CDKTR_WORKFLOW_DIRDefault workflow directoryworkflows
CDKTR_WORKFLOW_DIR_REFRESH_FREQUENCY_SInterval to refresh the workflow directory (seconds)60
CDKTR_SCHEDULER_START_POLL_FREQUENCY_MSInterval at which the scheduler checks if a workflow is ready to start (milliseconds)500
CDKTR_Q_PERSISTENCE_INTERVAL_MSTask queue persistence interval for principal recovery (milliseconds)1000
CDKTR_APP_DATA_DIRECTORYApp data directory for cdktr instances$HOME/.cdktr
CDKTR_DB_PATHPath to the main database for the principal instance$HOME/.cdktr/app.db
CDKTR_TUI_STATUS_REFRESH_INTERVAL_MSTUI refresh interval for principal status checks (milliseconds)1000
CDKTR_AGENT_HEARTBEAT_TIMEOUT_MSAgent heartbeat timeout - workflows marked as CRASHED if no heartbeat within this duration (milliseconds)30000