From 7eecadd8d64c77ba4118bb6397f7eac474868bfb Mon Sep 17 00:00:00 2001
From: nuthalapativarun <nuthalapativarun@gmail.com>
Date: Wed, 27 May 2026 04:21:20 -0700
Subject: [PATCH] fix: abort docker compose when OSS_JWT_SECRET is unset (#356)

Using :-ChangeMeInProduction silently starts the stack with a known
public signing key. Switch to :? so docker compose up exits with a
clear error when the variable is not provided.
---
 docker-compose.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docker-compose.yaml b/docker-compose.yaml
index f453449..d440aa1 100644
--- a/docker-compose.yaml
+++ b/docker-compose.yaml
@@ -173,7 +173,7 @@ services:
       TURN_SECRET: "${TURN_SECRET:-}"
       FORCE_TURN_RELAY: "${FORCE_TURN_RELAY:-false}"
 
-      OSS_JWT_SECRET: "${OSS_JWT_SECRET:-ChangeMeInProduction}"
+      OSS_JWT_SECRET: "${OSS_JWT_SECRET:?OSS_JWT_SECRET must be set to a strong secret}"
 
       # Telemetry
       ENABLE_TELEMETRY: "${ENABLE_TELEMETRY:-true}"