I used an Auto Scaling Group (ASG) to provision and shut down instances as required. (For reference, let's call that wait time IDLE_COUNT_THRESHOLD.) Scale in whenever that number is more than the JIBRIS_THRESHOLD and the Jibri containers have been IDLE for some time.Scale out as soon as the number of available Jibri containers in the pool drops below the JIBRIS_THRESHOLD. (For reference, let's call that JIBRIS_THRESHOLD.) The PlanĪs a single Jibri container could only record or stream one meet at a time, I intended to maintain a particular number of Jibri containers in the pool at any time. Jitsi is a free, open-source, out-of-the-box video conferencing solution. Jibri is a recording and streaming service for Jitsi. Thanks to the amazing people at the Jitsi Community Forum, I did end up finding bits and pieces of how one would go about architecting a sytem like this. Like any other true startup software engineer, I began reading through online forums. While it may come off as somewhat of a niche read, I believe this would potentially help you think about scaling any system in general.įirst things first, when I was presented with the problem, I did not have much experience with architecting. Ġ views autoscaling aws docker docker-swarm jibri jitsi jitsi-meet.You may repeat the creation of other usernames by running “prosodyctl register” as required.Posted on 29th July, 2021 by Preet Mishra Prosodyctl register roy MYsecurePasswordĪfter these changes, visiting – one could still create a room but it does not start until you are able to login with username “roy” and password “MYsecurePassword”. # CREATE A NEW ENTRY FOR THE FOLLOWING #Ĭp -a .ORIGINALĪnonymousdomain: '',Ĭp -a sip-communicator.properties To limit this, we need to create authentication for hosting rooms. That’s kinda worrying since you are “paying” for the resources. However, at this point, anyone and everyone could visit the URL and create a room for themselves. Visit and you should have JITSI MEET SERVER running. usr/share/jitsi-meet/scripts/install-letsencrypt-cert.shĬp -a interface_config.js interface_config.js.ORIGINAL Sh -c "echo 'deb stable/' > /etc/apt//jitsi-stable.list" With reference from and slightly adapted for my own purposes, I did the following:. This will ensure that your Debian instance will be allocated the same static public IP after reboots.Įdit your zone name records to include the following A 123.123.123.123 (static IP by LightSail) If you would like to keep the JITSI MEET SERVER, may I suggest you create a static IP at LighSail and assign it to the Debian instance. Linux instanceĬonfigure to open the following ports on the LightSail Debian instance TCP 22 Launch an instance on LightSail, I choose one which I think will be the bare minimum for JITSI MEET SERVER to function. If you have not heard of AWS LightSail, think of it as DigitalOcean by AWS □ Used an instance from AWS LightSail (simply because I was on the page and was describing how easy it was to invoke an instance as compared to the perceived “complexity” on the full AWS console). Here’s what I did on a slow Saturday late morning. They provide the ability for you to create your own room and start a call for free but whatever the reason, you might be looking for the ability to run your own JITSI MEET SERVER. JITSI MEET – More secure, more flexible, and completely free video conferencing
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |