Sravan
1128f9811a
- Broken images: UPLOADS_DIR/REC_DIR/TRANS_DIR were server/<dir> INSIDE the image,
so every deploy.sh rebuild wiped uploaded files — old images 404'd ('broken
image') though their DB rows survived. Make them env-overridable and point prod
at /data/uploads|recordings|transcripts (persistent volume), matching DB/downloads.
NOTE: files already lost to prior rebuilds can't be recovered; new uploads persist.
- Duplicate notifications: harden connectChatWs — close/detach any prior socket
before opening a new one and keep a single pending reconnect timer, so a flaky
reconnect can't leave two live sockets delivering every event/notification twice.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
66 lines
2.9 KiB
YAML
66 lines
2.9 KiB
YAML
# BizGaze Support — deployed behind the existing Nginx Proxy Manager.
|
|
# No host ports are published: NPM reaches this container by name on the
|
|
# shared `nginx_proxy_manager_default` network. TLS is terminated by NPM,
|
|
# which proxies https://remote.bizgaze.com -> bizgaze-support:8090.
|
|
services:
|
|
app:
|
|
build: .
|
|
image: bizgaze-support:latest
|
|
container_name: bizgaze-support
|
|
restart: unless-stopped
|
|
environment:
|
|
- PORT=8090
|
|
- DB_PATH=/data/data.db
|
|
# Desktop installers + auto-update feed live on the persistent volume so uploaded
|
|
# builds survive image rebuilds (a plain image path would be wiped on every deploy).
|
|
- DOWNLOADS_DIR=/data/downloads
|
|
# Chat uploads / recordings / transcripts on the persistent volume too, so they survive image
|
|
# rebuilds (otherwise old shared images 404 as "broken image" after every deploy).
|
|
- UPLOADS_DIR=/data/uploads
|
|
- REC_DIR=/data/recordings
|
|
- TRANS_DIR=/data/transcripts
|
|
# Secrets (TURN credentials, SSO_SECRET, BIZGAZE_WEBHOOK_URL, etc.) live in
|
|
# a .env file next to this compose file. It is gitignored — never committed.
|
|
# See .env.example for the expected keys.
|
|
env_file:
|
|
- path: .env
|
|
required: false
|
|
volumes:
|
|
- bizgaze_support_data:/data # persists data.db across rebuilds
|
|
networks:
|
|
- npm
|
|
|
|
# LiveKit SFU — meeting media server. Optional: only started/used when the app's .env has
|
|
# LIVEKIT_URL/API_KEY/API_SECRET set (otherwise meetings use the built-in P2P mesh). NPM proxies
|
|
# wss://livekit.bizgaze.com -> livekit:7880 (signaling); media flows over the published UDP/TCP
|
|
# ports below, NOT through NPM. Single-node (no Redis) — consistent with the app's single-instance rule.
|
|
livekit:
|
|
# v1.8+ implements the /rtc/v1 signaling path (protocol 17) that the bundled
|
|
# livekit-client@2.20 uses. On the older v1.7 the client fell back to the legacy path and
|
|
# track publishing broke (mic/cam wouldn't turn on). Keep this within one minor of the client.
|
|
image: livekit/livekit-server:v1.9
|
|
container_name: bizgaze-livekit
|
|
restart: unless-stopped
|
|
# Dormant by default: a normal `docker compose up -d` / deploy.sh does NOT start it. Enable SFU
|
|
# explicitly with `docker compose --profile sfu up -d` after setting the LIVEKIT_* vars (see DEPLOY.md).
|
|
profiles: ["sfu"]
|
|
command: --config /etc/livekit.yaml
|
|
environment:
|
|
# key: secret, sourced from the same .env as the app so both sign/verify with the same secret.
|
|
- "LIVEKIT_KEYS=${LIVEKIT_API_KEY}: ${LIVEKIT_API_SECRET}"
|
|
volumes:
|
|
- ./livekit.yaml:/etc/livekit.yaml:ro
|
|
ports:
|
|
- "7881:7881" # WebRTC over TCP (fallback)
|
|
- "50000:50000/udp" # single WebRTC media UDP port (must match livekit.yaml rtc.udp_port)
|
|
networks:
|
|
- npm
|
|
|
|
networks:
|
|
npm:
|
|
external: true
|
|
name: nginx_proxy_manager_default
|
|
|
|
volumes:
|
|
bizgaze_support_data:
|