For anyone looking to reproduce what worked for me:
Will get you a server running on
Check that this is working for you. You should now be able to make edits such as changing the text under “appDescription” in /lang/main.json and you should see that reflected on the main page. Be sure that’s working before you proceed.
Now, any changes you make to .js code should be visible in your localhost server. However, changes to .css, .html, and the toplevel config.js and inteface_config.js (among others??) won’t work because you are acquiring those files from the remote server (alpha.jisti.net).
You can address this by changing the file webpack.config.js. Look for the function
devServerProxyBypass(). Edit it to add:
and any other files that you know you want to be served from your local server instead of the backend server. This will tell webpack to bypass getting them from alpha.jisti.net - as long as they are called directly. (Thanks @gpatel-fr for this hint)
Now, within index.html, you need to change the lines at the end that include any .js file to be served locally instead of virtually (I think??) for example, from:
<script><!--#include virtual="/interface_config.js" --></script>
While you’re editing index.html, add something specific to your local version so you’ll know it’s working. For example, I changed line 31 to output “(local – TIME) index.html loaded:\t” so that looking at the console I’d know if I was loading the local version or the remote one.
Now you should be all set. Make another simple change to interface_config.js, for example edit the APP_NAME to say “Jitsi Meet - local” and see if that is how it now refers to itself in the browser tabs.
This all worked for me, as long as I specifically loaded
https://localhost:8080/index.html in my browser tab. Note, it doesn’t work if I don’t put in the /index.html part. And if I put anything else, including the name of any meeting other than “index.html” it will still load the remote version. But for my experimental purposes, it doesn’t matter because I am just meeting with myself at this point to try out new interface paradigms.
Finally - picking up on what @damencho said above, the
config.js file on alpha.jitsi.net is significantly different than the one in the repo you’ve downloaded. You should make a backup of yours then replace it with the code from alpha.jitsi.net/config.js, so that you are working properly with the alpha server that the nice jitsi folks have provided.
Finally, do all of this at your own risk and your mileage may vary – it is working for me for now, but it does feel like a bit of a hack. Thanks to @damencho and also to @artknight and @gpatel-fr for your breadcrumbs from the thread linked above.
@Apoorv_Jain, since you asked - here are the directions. Let me know if it works for you.