lzstealth/pulse-signage
1
0
Fork 0
Code Issues Pull Requests Actions Packages Activity

Configure remote player web pairing URL

Browse Source
This commit is contained in:
lzstealth
2026-09-22 20:54:33 +01:00
parent a4936b6a20
commit 99d61d04f3
2 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docker-compose/.env.remote.example
+3
View File
@@ -7,6 +7,9 @@ PULSE_SIGNAGE_SHARED_SECRET=""
# Remote player # Remote player
PLAYER_IDENTIFIER="player-remote" PLAYER_IDENTIFIER="player-remote"
# Public web application URL used for the pairing page in the QR code
WEB_PUBLIC_URL="https://signage.example.com"
# Optional URL used by the kiosk launcher when the remote player is directly reachable # Optional URL used by the kiosk launcher when the remote player is directly reachable
PLAYER_PUBLIC_URL="http://remote-player.example.com:8081" PLAYER_PUBLIC_URL="http://remote-player.example.com:8081"
docker-compose/docker-compose.remote.yml
+1
View File
@@ -11,6 +11,7 @@ services:
- "8081:8081" - "8081:8081"
environment: environment:
PLAYER_IDENTIFIER: ${PLAYER_IDENTIFIER:-player-remote} PLAYER_IDENTIFIER: ${PLAYER_IDENTIFIER:-player-remote}
WEB_PUBLIC_URL: ${WEB_PUBLIC_URL:?WEB_PUBLIC_URL must be set to the public web application URL}
PLAYER_PUBLIC_URL: ${PLAYER_PUBLIC_URL:-} PLAYER_PUBLIC_URL: ${PLAYER_PUBLIC_URL:-}
BRIDGE_PUBLIC_URL: ${BRIDGE_PUBLIC_URL:?BRIDGE_PUBLIC_URL must be set to a routable bridge URL} BRIDGE_PUBLIC_URL: ${BRIDGE_PUBLIC_URL:?BRIDGE_PUBLIC_URL must be set to a routable bridge URL}
PULSE_SIGNAGE_SHARED_SECRET: ${PULSE_SIGNAGE_SHARED_SECRET:-} PULSE_SIGNAGE_SHARED_SECRET: ${PULSE_SIGNAGE_SHARED_SECRET:-}