Desparately trying to understand how config.js is loaded.
(1) start a meeting through https://meet.jit.si/ and turn on ‘inspect/network’, There is no config.js in the network traces.
(2) I have my own self-hosted jitsi, and config.js is not in network trace either. Any change in config.js has no effect in selfhost/development.
I read some discussion, it says config.js is not loaded from the local build, but only from the server. I am fine as long as i can find config.js in the network trace, so that i know where the config.js is jitsi meet loading from.
(3) in the jitsi meet’s index.html, i see this line below – is this line supposed to be changed???
server side inclusion – that explains no network trace of config.js
One more question: if i do self-host on my dev machine, from where does web jitsi get all the config.js values? The self host could not do server inclusion, right?
If you refer to make dev, this is not hosting this is just a webpack dev proxy server running - proxying some requests in a way it works with a remote deployment but using the client web app that is built from the sources. In that case, it uses the index.html from the remote server, which includes the config.js from that deployment, making sense as you will be using it and you need its config.
By default it uses alpha jitsi net, if you do WEBPACK_DEV_SERVER_PROXY_TARGET='https://mydomain.com' make dev you can use your deployment for that.
I was referring to “make dev”. All is clear now: the config.js is included in the server’s index.html, via the webpack dev proxy. What’s the method to really self host config.js through the development process, without running a server deployment?