feat: support managed bot autostart#2
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d8a0d2c3d9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| auto_start_bot = os.environ.get( | ||
| "DIGITAL_MATE_AUTO_START_BOT", "" | ||
| ).strip().lower() in {"1", "true", "yes", "on"} |
There was a problem hiding this comment.
Honor .env for the autostart flag
When DIGITAL_MATE_AUTO_START_BOT=true is added to the project .env (the same place this commit documents the setting), the dashboard still will not autostart the bot because this check reads only os.environ. Other dashboard settings such as DASHBOARD_API_KEY fall back to SettingsService, and the CLI does not load .env into os.environ, so installs that configure the new option in .env and run digital-mate serve will continue to report the bot as stopped unless the variable is separately exported.
Useful? React with 👍 / 👎.
What changed
DIGITAL_MATE_AUTO_START_BOTdashboard lifecycle settingValidation
python -m pytest tests/test_web.py -q -W error::DeprecationWarninggit diff --check