We have now a dedicated Jibri server. At each Jitsi instance recording and/or streaming needs to be activated in the `domain-config.js` settings.
We have now a dedicated Jibri server. At each Jitsi instance recording and/or streaming needs to be activated in the `domain-config.js` settings.
## Recorder setup
On serles server we have defined 12 ALSA loopbacks and run 6 jibri dockers defined in `~/jibri-docker/jibri6recorders.yml`
Recordings are dumped first in ~/jibri-docker/recordings
After recording they are moved by script ~/jibri-docker/recordings/finalize.sh to `/var/www/rec/` and original files are deleted.
Logfile is `~/jibri-docker/recordings/publish_recording.log`
Fire up 6 recorders:
Fire up 6 recorders:
root@serles ~/jibri-docker # docker-compose -f jibri6recorders.yml up -d
root@serles ~/jibri-docker # docker-compose -f jibri6recorders.yml up -d
Jibri always listens to the base URL of the service (meet.fairkom.net / run.fairmeeting.net) and uses the config settings and watermark logo defined in its config.js, there increase video bandwidth and add
## Watermark logo
Jibri always listens to the base URL of the service (meet.fairkom.net / run.fairmeeting.net) and uses the config settings and watermark logo defined in its config.js, there we also increase video bandwidth and add
hiddenDomain: 'recorder.meet.fairkom.net',
hiddenDomain: 'recorder.meet.fairkom.net',
...
@@ -12,6 +21,8 @@ Jibri always listens to the base URL of the service (meet.fairkom.net / run.fair
...
@@ -12,6 +21,8 @@ Jibri always listens to the base URL of the service (meet.fairkom.net / run.fair
To be downloaded at `rec1.fairmeeting.net/roomname`.
To be downloaded at `rec1.fairmeeting.net/roomname`.
Or go to `rec1.fairmeeting.net` and enter room name into a search field.
## Streaming
## Streaming
Enter as streaming key a YouTube key or any other streaming server as a target:
Enter as streaming key a YouTube key or any other streaming server as a target: