Closed minnixtx closed 2 years ago
Never mind it seems maybe I must either upgrade or create a config.json.
Wait I'm on the latest version of jitsi-meet and jibri and I have neither config.json or config.js installed. Is this something I need to create myself?
root@jitsi:~# dpkg -l | grep jitsi
ii jitsi-meet 2.0.7648-1 all WebRTC JavaScript video conferences
ii jitsi-meet-prosody 1.0.6447-1 all Prosody configuration for Jitsi Meet
ii jitsi-meet-turnserver 1.0.6447-1 all Configures coturn to be used with Jitsi Meet
ii jitsi-meet-web 1.0.6447-1 all WebRTC JavaScript video conferences
ii jitsi-meet-web-config 1.0.6447-1 all Configuration for web serving of Jitsi Meet
ii jitsi-videobridge2 2.2-22-g42bc1b99-1 all WebRTC compatible Selective Forwarding Unit (SFU)
root@jibri:~# dpkg -l | grep jibri
ii jibri 8.0-137-g260cee3-1 all Jibri
Running jibri on Ubuntu 20 and jitsi on Debian 11, both native installs on X86-64
config.js is in /etc/jitsi/meet
config.js is in /etc/jitsi/meet
ok, i was looking for config.js when I should have been looking for mydomain.config.js.
Also in the jibri README at the end it says "Note: Make sure to update Jibri's config.json appropriately to match any config done above."
Is this referring to /etc/jitsi/jibri/jibri.conf ?
Same issue https://github.com/jitsi/jibri/issues/434#issue-983593755
Guess I should have searched better. So jibri.conf is what we should be using it looks like and README just needs updating. I'll close this now.
Just what the title says. Does it need to be updated?