Luis Guzmán
de59dc7d24
|
||
|---|---|---|
| files | ||
| images | ||
| mode | ||
| tools | ||
| .gitignore | ||
| LICENSE | ||
| README.md | ||
| add-jibri-node.sh | ||
| add-jvb2-node.sh | ||
| etherpad.sh | ||
| grafana.sh | ||
| jigasi.sh | ||
| jitsi-updater.sh | ||
| jm-bm.sh | ||
| jra_nextcloud.sh | ||
| quick_jibri_installer.sh | ||
README.md
Quick Jibri Installer
Bash installer for Jibri on Ubuntu LTS based systems using nginx as default webserver.
Usage
As for our current latest release, as we have integrated more and more features, we highly recommend to use a purpose specific-newly spawn server to host the jitsi-meet framework, making sure you stick to the requirements and recommendations as much as possible, in order to avoid issues.
Main Server
Login into your clean server, clone git repository and run the installer,
git clone https://github.com/switnet-ltd/quick-jibri-installer
cd quick-jibri-installer
bash quick-jibri-installer.sh
Add Jibri node
Copy the modified add-jibri-node.sh file from your early cloned installation directory once the installation is completed, to the new server meant to be a jibri node using your preferred method, then run it
WARNING: This file contains sensitive information from your setup, please handle with care.
bash add-jibri-node.sh
Add JVB2 node
Copy the modified add-jvb2-node.sh file from your early cloned installation directory once the installation is completed, to the new server meant to be a jibri node using your preferred method, then run it
WARNING: This file contains sensitive information from your setup, please handle with care.
bash add-jvb2-node.sh
Check more details on our wiki.
Requirements
- Clean VM/VPS/Server using Ubuntu LTS
- Valid domain with DNS record, mandatory for SSL certs via Let's Encrypt.
- Ports open for ACME (SSL) interaction & validation.
- Highly recommended: 8 GB RAM / 4 Cores.
- Webcam
Jigasi Transcript
- SIP account
- Google Cloud Account with Billing setup.
Jibri Recodings Access via Nextcloud
- Valid domain with DNS record for Nextcloud SSL.
Kernel warning
For AWS users or any cloud service provider that might use their own kernel on their products (servers/vm/vps), might cause Jibri failure to start due not allowing snd_aloop module.
Make sure that you update your grub to boot the right one.
Feel free to use our test-jibri-env.sh tool to find some details on your current setup.
Features
- Enabled Session Recording using Jibri
- Enabled Jitsi Electron app detection server side.
- Standalone SSL Certbot/LE implementation
- Jigasi Transcript - Speech to Text powered by Google API
- JRA (Jibri Recordings Access) via Nextcloud
- Improved recurring updater
- Customized brandless mode
- Setting up custom interface_config.js
- Grafana Dashboard
- Lobby Rooms via
- Local (Secure Rooms) auth
- JWT auth
- None
- Conference Duration via
- Local (Secure Rooms) auth
- JWT auth
- None
- Automatic Jibri nodes network sync (see more).
- JVB2 nodes network.
- JWT auth.
- Rename Jibri folder with name room + date.
Tools
- Jibri Environment Tester
- Jibri Conf Upgrader (late 2020).
- Selenium Grid via Docker
Optional custom changes
- Optional default language
- Option to enable Secure Rooms
- Option to enable Welcome Page
Modes
- Custom High Performance config
Custom changes
- Start with video muted by default
- Start with audio muted but moderator
- Set displayname as not required since jibri can't set it up.
- Disabled BETA Blur my background
Documentation
- Please check our wiki for further documentation.
Please note: This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY.
SwITNet Ltd © - 2020, https://switnet.net/