/etc/jitsi/jibri/config.json is it still exists

Open baselrabia opened this issue 4 years ago • 2 comments

https://github.com/jitsi/jibri/blob/9871ba137cb759d22d31e5e1f7cfade8e8b4ca65/resources/debian-package/opt/jitsi/jibri/launch.sh#L3

why the config attribute refers to "/etc/jitsi/jibri/config.json" which does not exist anymore not to /etc/jitsi/jibri/jibri.conf which has the config is it right to be like that ??

Aug 31 '21 08:08 baselrabia

@baselrabia Docker setup still uses config.json for jibri config. I think this might be the reason why config.json is still present.

AFAIK if we are using jibri.conf then it has high precedence over config.json. @bbaldino Can you please confirm?

Sep 01 '21 04:09 prayagsingh

config.json has a higher preference than the new config, in order to obey any settings a user may have had previously. didn't know docker was still using config.json, though.

Sep 01 '21 23:09 bbaldino