External/roboco
1
0
Fork 0
mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix(deploy): arm the Telegram trio by default in the NAS compose per the arm-new-flags convention

Browse Source
This commit is contained in:
Renn F
2026-07-18 05:21:22 +02:00
parent 59594d794a
commit e3ec24f58f
3 changed files with 29 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docker-compose.yml
+10 -8
View File
@@ -530,12 +530,13 @@ services:
ROBOCO_ORG_MEMORY_ENABLED: ${ROBOCO_ORG_MEMORY_ENABLED:-true}
ROBOCO_X_ENGINE_ENABLED: ${ROBOCO_X_ENGINE_ENABLED:-true}
# Telegram notifications bridge: best-effort DMs to the CEO on escalation
# + completion. Config default is OFF; not yet armed here (needs stored
# bot-token + chat-id credentials regardless of this flag).
ROBOCO_TELEGRAM_ENABLED: ${ROBOCO_TELEGRAM_ENABLED:-false}
# + completion. Armed by default here per the NAS-compose convention
# (new flags ship ON unless the CEO opts out); inert without stored
# bot-token + chat-id credentials regardless of this flag.
ROBOCO_TELEGRAM_ENABLED: ${ROBOCO_TELEGRAM_ENABLED:-true}
# Telegram V2 — inbound commands + actionable approve/reject buttons.
# Armed here (sub-switch on top of the still-off ROBOCO_TELEGRAM_ENABLED
# above); the whole bridge stays inert until that flag AND credentials
# Armed here (sub-switch of ROBOCO_TELEGRAM_ENABLED above); the whole
# bridge stays inert until that flag AND credentials
# are both set, so arming this alone does nothing yet.
ROBOCO_TELEGRAM_INBOUND_ENABLED: ${ROBOCO_TELEGRAM_INBOUND_ENABLED:-true}
# Telegram Mini App sign-in: validates Telegram's signed WebApp initData
@@ -543,9 +544,10 @@ services:
# so the CEO's phone becomes an authenticated panel client. Requires
# ROBOCO_CLOUD_AUTH_ENABLED=true (startup fails loud otherwise) AND a
# public HTTPS origin (the cookie is secure-only, and Telegram itself
# only opens Mini Apps over https). Default OFF; not armed here — the
# operator flips it on once TLS + cloud-auth creds are both live.
ROBOCO_TELEGRAM_MINIAPP_ENABLED: ${ROBOCO_TELEGRAM_MINIAPP_ENABLED:-false}
# only opens Mini Apps over https). Armed by default per the NAS-compose
# convention — NOTE: boot fails loud if cloud auth is disabled/unseeded,
# so a cloud-auth-off .env must also set this false.
ROBOCO_TELEGRAM_MINIAPP_ENABLED: ${ROBOCO_TELEGRAM_MINIAPP_ENABLED:-true}
ROBOCO_OBSIDIAN_VAULT_ENABLED: ${ROBOCO_OBSIDIAN_VAULT_ENABLED:-true}
ROBOCO_VAULT_PATH: ${ROBOCO_VAULT_PATH:-/app/vault}
ROBOCO_VAULT_INTAKE_ENABLED: ${ROBOCO_VAULT_INTAKE_ENABLED:-true}