eb22e01f31
The jitsi video bridge (jvb) appears to be the main component we'll need to scale up to handle more users on meetpad. Start preliminary ansiblification of scale out jvb hosts. Note this requires each new jvb to run on a separate host as the jvb docker images seem to rely on $HOSTNAME to uniquely identify each jvb. Change-Id: If6d055b6ec163d4a9d912bee9a9912f5a7b58125
27 lines
726 B
YAML
27 lines
726 B
YAML
# Based on https://github.com/jitsi/docker-jitsi-meet/blob/df404476160526d8512fb23b606965b98f7f25f3/docker-compose.yml
|
|
# Licensed under the ASL v2.
|
|
|
|
version: '2'
|
|
|
|
services:
|
|
# Video bridge
|
|
jvb:
|
|
image: docker.io/jitsi/jvb
|
|
network_mode: host
|
|
volumes:
|
|
- ${CONFIG}/jvb:/config
|
|
environment:
|
|
- DOCKER_HOST_ADDRESS
|
|
- XMPP_AUTH_DOMAIN
|
|
- XMPP_INTERNAL_MUC_DOMAIN
|
|
- XMPP_SERVER
|
|
- JVB_AUTH_USER
|
|
- JVB_AUTH_PASSWORD
|
|
- JVB_BREWERY_MUC
|
|
- JVB_PORT
|
|
- JVB_TCP_HARVESTER_DISABLED
|
|
- JVB_TCP_PORT
|
|
- JVB_STUN_SERVERS
|
|
- JVB_ENABLE_APIS
|
|
- TZ
|