mirror of
https://github.com/vector-im/element-call.git
synced 2024-11-21 00:28:08 +08:00
e98740d6f2
I recently tried to use the dev configs with a local homeserver and found that the configuration was not compatible with this. We need to relax the network isolation and TLS cert verification requirements for fully local development to be possible.
49 lines
1.2 KiB
YAML
49 lines
1.2 KiB
YAML
version: "3.9"
|
|
|
|
networks:
|
|
lkbackend:
|
|
|
|
services:
|
|
auth-service:
|
|
image: ghcr.io/element-hq/lk-jwt-service:latest-ci
|
|
hostname: auth-server
|
|
# Use host network in case the configured homeserver runs on localhost
|
|
network_mode: host
|
|
environment:
|
|
- LK_JWT_PORT=8881
|
|
- LIVEKIT_URL=ws://localhost:7880
|
|
- LIVEKIT_KEY=devkey
|
|
- LIVEKIT_SECRET=secret
|
|
# 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
|
|
deploy:
|
|
restart_policy:
|
|
condition: on-failure
|
|
networks:
|
|
- lkbackend
|
|
|
|
livekit:
|
|
image: livekit/livekit-server:latest
|
|
command: --dev --config /etc/livekit.yaml
|
|
restart: unless-stopped
|
|
ports:
|
|
- "7880:7880"
|
|
- "7881:7881"
|
|
- "7882:7882"
|
|
- "50100-50200:50100-50200"
|
|
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
|