How To - intulse/jitsi-meet GitHub Wiki

Get the Latest Code from Jitsi

Jitsi is an open source project in Github. There are lots of pushes made to Jitsi, but not all of those changes get tested thoroughly. In order to ensure the code we pull down to our server is tested (at least in part) by the Jitsi team, we need to make sure we are only pulling down stable Jitsi releases. So, if you want to upgrade to the latest Jitsi code, you will need to search through the Jitsi Meet repository using the stable tag and find the latest branch with that tag. You can also see the full list of stable releases at:

https://github.com/jitsi/jitsi-meet/releases

Deploy Changes

  1. Deploy your changes to the Intulse branch

  2. Log into the server the Jitsi Meet instance is hosted on

  3. Run the following commands

    • git pull

      • (NOTE: This will pop up a commit message screen; just click CTRL + X to save and exit)
    • make

    • sudo ./deploy-local.sh

Set Up A Virtual Mac Machine for Testing

It is important that Intulse Meeting works on a wide variety of devices. Setting up a Mac virtual machine was very troublesome, because Virtual Box is not built to allow Macs natively. However, after trying a few different tutorials, I managed to find one that worked well. Please follow the following tutorial to setup your virtual Mac. Also note, once you complete this tutorial, you will then need to upgrade the machine to the latest Mac OS using the Mac software update feature on the machine itself:

https://techsprobe.com/install-macos-big-sur-on-virtualbox-on-windows-pc/#Step_Seven_-_Install_macOS_Big_Sur_on_VirtualBox_on_Windows_PC

Deploying Updates to Config.js

Making changes to the config.js in the Jitsi Meet repo gives gives us access to git history on that file. After changes are pushed to the repo apply the changes with this script:

git fetch && git pull;
cp ~/jitsi-meet/config.js /etc/jitsi/meet/<jitsi-domain>-config.js;
systemctl restart jitsi-videobridge2.service prosody.service;

Config Mobile in Browser access

There are two settings that currently (04/2024) control access to Jitsi meetings via the mobile browser. These changes ideally should be made in the Intulse Jitsi repo prior to deploying the build.

  • Enable the mobile browser in interface_config.js: set MOBILE_APP_PROMO to true or undefined (which defaults to true).

To change this value on the server: cd /usr/share/jitsi-meet, open interface_config.js. The change is applied once you save the file.

  • Disable the "download the mobile app" overlay in config.js: set deeplinking.disable = true.

To change this value after deployment, it is best to add deeplinking: { disabled: true }, to the configOverwrite object in the JitsiMeetOptions passed to the JitsiMeetExternalAPI. This can be found in meeting.component.ts in the most recent version of IntulseMeetings angular project.

How to redirect from meet.intul.se to meet.intulse.com

Place this in the /usr/share/jitsi-meet/index.html

<script>if (window.self === window.top) { window.location = "https://meet.intulse.com" }</script>
⚠️ **GitHub.com Fallback** ⚠️