How to manage the loading [domain]-config.js vs config.js

Dear all,

If I weel understand, [domain]-config.js is (will be) deprecated.
I noticed some issues by using config.js. For instance “startWithAudioMuted: true,”
So even if it is not academic I rename config.js to be sure it wont be load.

My questions: how to manage properly the settings between [domain]-config.js and config.js
Where can I decide which one to load rather than the other?


The deprecation is for interface config jitsi-meet/interface_config.js at f84f7332b9205652a7e9cd8772d05c6fd98e0329 · jitsi/jitsi-meet · GitHub

I’m not sure what do you mean by [domain]-config.js, this is the config in /etc/jitsi/meet and this is not going away. config.js is the name of the file in the source code and it is like a template. Once the config is changed it goes in /etc/jitsi/meet folder as [domain]-config.js

Thanks for your feedback @damencho
I was talking about these two files :slight_smile:

  • /etc/jitsi/meet/[domaine]-config.js
  • /usr/share/jitsi-meet-web-config/config.js
    so either we modify directly [domaine]-config.js or we modify config.js.
    If I well understand, once [domaine]-config.js is set it is strongly recommended do not modify config.js because this file will overwrite the file [domaine]-config.js?
    Am I right?

This one is used only once, when initially installing and this is the template of the config.js that goes in /etc/. You don’t touch it, you only modify the one in /etc/jitsi/meet/[domaine]-config.js

1 Like