chore(deploy): wire OPENAI_API_KEY + LLM_ENABLED for LLM chat activation (#960) #1178

Merged

bot-backend merged 1 commit from chore/deploy-llm-env-960 into main

2026-06-09 08:55:19 +00:00

Author	SHA1	Message	Date
Light1YT	98ecdecb5b	chore(deploy): wire OPENAI_API_KEY + LLM_ENABLED into prod env for LLM chat All checks were successful CI / changes (push) Successful in 6s Details CI / backend-tests (push) Has been skipped Details CI / frontend-tests (push) Has been skipped Details CI / changes (pull_request) Successful in 5s Details CI / backend-tests (pull_request) Has been skipped Details CI / frontend-tests (pull_request) Has been skipped Details Deploy / changes (push) Successful in 5s Details Deploy / build-worker (push) Successful in 28s Details Deploy / build-backend (push) Successful in 30s Details Deploy / build-frontend (push) Successful in 28s Details Deploy / deploy (push) Successful in 1m1s Details Forward OPENAI_API_KEY (Forgejo secret) and LLM_ENABLED (Forgejo actions variable) into the SSH deploy and write them to backend/.env.runtime ONLY when non-empty, so the LLM chat (#960/#957) stays dormant (llm_enabled=False, openai_api_key=None) until BOTH are set in Forgejo. Mirrors the OBJECTIVE_API_KEY wiring (env block + envs list + idempotent .env.runtime grep-sed-or-printf), but guarded by [ -n ] so an unset secret/var writes nothing. No literal key (refs only). Compose header documents both as optional. .env.runtime is shared by backend+worker+beat. Refs #960	2026-06-09 13:51:41 +05:00