NewConfigurationUpdated Aug 30, 20268 min read
Configure region, browser sessions, and delays
The bot keeps its existing config.ini workflow while allowing Docker deployments to override settings through MISSIONCHIEF_* environment variables.
01
Core settings
- MISSIONCHIEF_REGION selects a supported region such as UK or US.
- MISSIONCHIEF_USERNAME and MISSIONCHIEF_PASSWORD provide runtime credentials.
- MISSIONCHIEF_HEADLESS controls browser visibility and defaults to headless in the container.
- MISSIONCHIEF_BROWSERS controls the browser pool size.
02
Mission and delay controls
Dispatch mode, concurrent missions, incomplete-mission behavior, automatic tasks, and mission/transport delays remain available in config.ini. The Docker image also supports MISSIONCHIEF_* overrides for these values.
03
Credential safety
The local config.ini is excluded from the Docker build context. Use a private .env file or a mounted config file at runtime, and do not commit either one.
Was this guide useful?Tell us what could be clearer →