-
Inbuilt Support for streaming to any rtmp server.
-
Stream to Facebook.
-
Inbuilt support for Rclone.
-
Store your recordings to any S3 compatible storage.
-
Store your recordings to Google Drive.
- Use
examples/jibri.yml
with docker-compose. - Use
examples/stack-jibri.yml
withdocker stack deploy
. - Use
examples/jibri-k8s
directory to setup jibri on k8s. Useexamples/jibri-k8s/kustomization.yaml
for deployment.Kustomize
version isv4.0.5
. - Look for
update_this
and change the value accordingly. Also changemeet.example.com
with a valid URL.
NOTE 1: It is mandatory to map /dev/shm
else chrome crashes when screen-share is enabled
NOTE 2: Here I'm using external
network in both the files. Please change it accordingly.
NOTE 3: Please take the necessary steps to secure the AWS keys when using with rclone.
- docker-compose: working with
1920x1080
- docker-swarm: working with
1920x1080
- k8s: working with
1280x720
resolution only. With1920x1080
, the memory consumption reached up to 7.5 GiB and vCPU up to 6 and after 10 minutes recording crashed. With resolution1280x720
, recording went fine. Tested in 50 minutes meeting with 3 participants and with/without screen-sharing. In order to lower down the resolution to1280x720
, we have to changeVirtual 1920 1080
withVirtual 1280 720
inxorg-video-dummy.conf
file and set env variableJIBRI_FFMPEG_RESOLUTION="1280x720"
.
K8s resource usage with 1280x720 resolution with 3 participants in a meeting: Stable