Files
multica/scripts
Bohan Jiangandmultica-agent 53578958bc fix(selfhost): pass MULTICA_DINGTALK_SECRET_KEY through and guard integration keys (#8617)
The backend service environment in docker-compose.selfhost.yml is an
explicit allowlist, and MULTICA_DINGTALK_SECRET_KEY was never on it:
Docker self-hosters who set the key in .env still got a disabled DingTalk
integration. Telegram had the same gap until #8611.

- Map MULTICA_DINGTALK_SECRET_KEY into the backend service.
- Document MULTICA_SLACK_SECRET_KEY and MULTICA_TELEGRAM_SECRET_KEY in
  .env.example next to the other channel keys.
- Extend selfhost-config.test.sh: every key the server loads through
  secretbox.LoadKey must be mapped in docker-compose.selfhost.yml and
  listed in .env.example. The list comes from the server, not the docs,
  because Telegram's key was missing from both.
- Run script-checks when server/cmd/server/router.go changes, where the
  integration gates live, so a new channel key trips the guard in the PR
  that adds it.

Co-authored-by: multica-agent <[email protected]>
2026-09-21 12:07:23 +08:00
..