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

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
+9 -6
View File
@@ -203,17 +203,20 @@ ROBOCO_DB_NETWORK_ISOLATED=true
# =============================================================================
# Telegram notifications bridge — V1 (outbound DMs) / V2 (inbound commands) /
# V3 (Mini App sign-in) — all default OFF; inert without stored bot-token +
# chat-id credentials (set via the panel, not env) regardless of these flags.
# V3 (Mini App sign-in). The NAS compose (docker-compose.yml) arms all three
# by DEFAULT per the arm-new-flags convention; set false here to opt out.
# Inert without stored bot-token + chat-id credentials (set via the panel,
# not env) regardless of these flags. Config-code default (no compose) is OFF.
# =============================================================================
# ROBOCO_TELEGRAM_ENABLED=false
# ROBOCO_TELEGRAM_ENABLED=true
# V2: inbound commands + actionable approve/reject buttons. Sub-switch on top
# of ROBOCO_TELEGRAM_ENABLED above — arming this alone does nothing.
# ROBOCO_TELEGRAM_INBOUND_ENABLED=false
# ROBOCO_TELEGRAM_INBOUND_ENABLED=true
# V3: Telegram Mini App sign-in — mints a cloud-auth session cookie for the
# CEO's phone. Requires ROBOCO_CLOUD_AUTH_ENABLED=true (startup fails loud
# otherwise) AND a public HTTPS origin (Mini Apps only open over https).
# ROBOCO_TELEGRAM_MINIAPP_ENABLED=false
# otherwise — a cloud-auth-off .env must set this false too) AND a public
# HTTPS origin (Mini Apps only open over https).
# ROBOCO_TELEGRAM_MINIAPP_ENABLED=true
# =============================================================================
# Model routing strictness