It is happening to me that with some functionalities that do not work and, apparently, they are deprecated seeing that in the reference file interface_config.js (https://github.com/jitsi/jitsi-meet/blob/master/interface_config.js ) I see the message “This file is considered deprecated. All options will eventually be moved to config.js, and no new options should be added here.”
Furthermore, the Handbook goes on to say that “You can override options set in the config.js file and the interface_config.js file using the configOverwrite and interfaceConfigOverwrite objects, respectively.”
But, the interface_config.js wasn’t deprecated?
I would like to please shed some light on this confusion and if you can update or post the new way to implement the IFrame settings since I work with external js.
config.js is what the frontend reads to connect to the meeting. When you use the IFrame API you only need to specify the domain, because then we can get the config.js ourselves from https://DOMAIN/config.js
You can then use configOverride to change the default behavior (what’s on config.js) with your chosen values.
All this I understand and I have it working.
What I would need is an example of use (as there is in the Handbook) but with the new way of using config.js to be able to start adapting everything since I have several projects that I must normalize