2023-06-12 21:52:27 +08:00
|
|
|
version: "3.9"
|
|
|
|
|
|
|
|
networks:
|
|
|
|
lkbackend:
|
|
|
|
|
|
|
|
services:
|
|
|
|
auth-service:
|
2023-12-13 04:02:27 +08:00
|
|
|
image: ghcr.io/element-hq/lk-jwt-service:latest-ci
|
2023-06-12 21:52:27 +08:00
|
|
|
hostname: auth-server
|
2024-09-27 02:11:40 +08:00
|
|
|
# Use host network in case the configured homeserver runs on localhost
|
|
|
|
network_mode: host
|
2023-06-12 21:52:27 +08:00
|
|
|
environment:
|
2024-09-27 02:11:40 +08:00
|
|
|
- LK_JWT_PORT=8881
|
2023-07-05 01:57:35 +08:00
|
|
|
- LIVEKIT_URL=ws://localhost:7880
|
|
|
|
- LIVEKIT_KEY=devkey
|
|
|
|
- LIVEKIT_SECRET=secret
|
2024-09-27 02:11:40 +08:00
|
|
|
# If the configured homeserver runs on localhost, it'll probably be using
|
|
|
|
# a self-signed certificate
|
|
|
|
- LIVEKIT_INSECURE_SKIP_VERIFY_TLS=YES_I_KNOW_WHAT_I_AM_DOING
|
2023-06-12 21:52:27 +08:00
|
|
|
deploy:
|
|
|
|
restart_policy:
|
|
|
|
condition: on-failure
|
|
|
|
networks:
|
|
|
|
- lkbackend
|
|
|
|
|
|
|
|
livekit:
|
|
|
|
image: livekit/livekit-server:latest
|
|
|
|
command: --dev --config /etc/livekit.yaml
|
|
|
|
restart: unless-stopped
|
2024-09-27 04:53:45 +08:00
|
|
|
# The SFU seems to work far more reliably when we let it share the host
|
|
|
|
# network rather than opening specific ports (but why?? we're not missing
|
|
|
|
# any…)
|
|
|
|
network_mode: host
|
|
|
|
# ports:
|
2024-09-28 04:35:39 +08:00
|
|
|
# - "7880:7880/tcp"
|
|
|
|
# - "7881:7881/tcp"
|
|
|
|
# - "7882:7882/tcp"
|
2024-10-18 03:14:12 +08:00
|
|
|
# - "50100-50200:50100-50200/udp"
|
2023-06-12 21:52:27 +08:00
|
|
|
volumes:
|
|
|
|
- ./backend/livekit.yaml:/etc/livekit.yaml
|
|
|
|
networks:
|
|
|
|
- lkbackend
|
|
|
|
|
|
|
|
redis:
|
|
|
|
image: redis:6-alpine
|
|
|
|
command: redis-server /etc/redis.conf
|
|
|
|
ports:
|
|
|
|
- 6379:6379
|
|
|
|
volumes:
|
|
|
|
- ./backend/redis.conf:/etc/redis.conf
|
|
|
|
networks:
|
|
|
|
- lkbackend
|