jibri: add jibri service
This commit is contained in:
committed by
Saúl Ibarra Corretgé
parent
af305af880
commit
ffa017b74d
43
env.example
43
env.example
@@ -246,6 +246,49 @@ JIGASI_PORT_MAX=20050
|
||||
# the docker host to ${CONFIG}/jigasi/key.json and to enable this setting:
|
||||
#GOOGLE_APPLICATION_CREDENTIALS=/config/key.json
|
||||
|
||||
# Enable recording
|
||||
#ENABLE_RECORDING=1
|
||||
|
||||
# XMPP domain for the jibri recorder
|
||||
XMPP_RECORDER_DOMAIN=recorder.meet.jitsi
|
||||
|
||||
# XMPP recorder user for Jibri client connections.
|
||||
JIBRI_RECORDER_USER=recorder
|
||||
|
||||
# XMPP recorder password for Jibri client connections.
|
||||
JIBRI_RECORDER_PASSWORD=passw0rd
|
||||
|
||||
# Directory for recordings inside Jibri container.
|
||||
JIBRI_RECORDING_DIR=/config/recordings
|
||||
|
||||
# The finalizing script. Will run after recording is complete.
|
||||
JIBRI_FINALIZE_RECORDING_SCRIPT_PATH=/config/finalize.sh
|
||||
|
||||
# XMPP user for Jibri client connections.
|
||||
JIBRI_XMPP_USER=jibri
|
||||
|
||||
# XMPP password for Jibri client connections.
|
||||
JIBRI_XMPP_PASSWORD=passw0rd
|
||||
|
||||
# MUC name for the Jibri pool.
|
||||
JIBRI_BREWERY_MUC=jibribrewery
|
||||
|
||||
# MUC connection timeout
|
||||
JIBRI_PENDING_TIMEOUT=90
|
||||
|
||||
# When jibri gets a request to start a service for a room, the room
|
||||
# jid will look like: roomName@optional.prefixes.subdomain.xmpp_domain
|
||||
# We'll build the url for the call by transforming that into:
|
||||
# https://xmpp_domain/subdomain/roomName
|
||||
# So if there are any prefixes in the jid (like jitsi meet, which
|
||||
# has its participants join a muc at conference.xmpp_domain) then
|
||||
# list that prefix here so it can be stripped out to generate
|
||||
# the call url correctly.
|
||||
JIBRI_STRIP_DOMAIN_JID=muc
|
||||
|
||||
# Directory for logs inside Jibri container.
|
||||
JIBRI_LOGS_DIR=/config/logs
|
||||
|
||||
# Disable HTTPS. This can be useful if TLS connections are going to be handled outside of this setup.
|
||||
#DISABLE_HTTPS=1
|
||||
|
||||
|
||||
Reference in New Issue
Block a user