Search results

Due to Jitsi’s modular, opensource, and highly configurable nature, there are many different architecture variations available when deploying a Jitsi ecosystem. This posting attempts to summarize, some more theoretical for the sake of discussion and analysis, a wide range of variants to consider for different implementations. Which Jitsi Architecture Variant to choose is based on each individual's specific scope and budget. Each successive variation tends to be more complicated than the prior variant. Note that these are NOT Jitsi official variations or terminology. These variation distinctions were created by Hawke Robinson as an attempt to bring some order to the many different potential approaches, and increase clarity when considering scalability, features, and budget constraints.

This is a reading list for those interested in learning more about Information Security (InfoSec).

Every profession is rife with buzzwords, and tech is replete with them. The specific details change, though the basics remain the same, and often recycle old-as-new every 20 years or so. This posting discusses the current bandwagon buzzwords about old-is-new microservices and monoliths primarily, though with some ancillary mentions regarding containerization, and more on Jitsi.

I am tasked with extensive load testing of Jitsi and related components. There have been a number of challenges just getting the tests to work on the scale needed (minimum 5k users, preferably 20k, but that can be extrapolated from the 5k). But just trying to get to 5k continues to be a challenge due being back in the 1970s and the popularity of "the cloud". I once again have to deal with the equivalent of the IBM engineers and begging for resource access to do my job... Anyway, here are updates on how it is going...

I am working on a very extensive load-testing for capacity planning project analyzing Jitsi and various related components in educational and other settings, for my current employer. In the current load-testing I have hit a hard limit around 600-650 users for a default-install standalone all-in-one Jitsi server. This is not expected behavior. I am hoping the JItsi community can help determine if it is as simple as a configuration tweak, or if it is a more serious bug.

I am working on a longitudinal series of projects that heavily involve the use of Jitsi, especially in educational settings. This is for large scale environments that have highly demanding loads, and are intended as Zoom replacements in the USA and worldwide. This is just one of a number of components. Today was great to finally reach the 1,000 simulated video users load test basic baseline. Next goal is 5,000+, and then adding in additional features and still trying to keep it all working on this scale (recordings, transcriptions, closed captioning, intricate chat options, complex permissions managements, file management, and much more). Great things happening!

Containerized selenium + chrome + terraform + docker + docker-compose + jitsi + malleus jitsificus dockerized fails.

Odoo 12's default test outbound email template attempts to send email to noreply@odoo.com. This needs to be changed to something useful in a production setup.

Since Odoo 13 was so inherently unstable we moved to Odoo 12 (had to fresh install, no backward migration option). This posting covers file and data size considerations.

Here is a great free app compatible with Odoo 12 to allow public users to book appointments easily using the app s2u_online_appointment.