#JITSI MEET NGINX INSTALL#
#JITSI MEET NGINX ANDROID#
#JITSI MEET NGINX PASSWORD#

Prerequisites: you have an RPi4 running gentoo-on-rpi-64bit.

Have fun, and please report any issues either in this thread (preferred) or via email to if you are instead looking for a quick way to get an x86_64 Gentoo Jitsi server up and running, you might like to take a look at my nspawn-gentoo-jitsi-meet project on GitHub! Should you wish to have your Jitsi server start automatically on boot, finally follow the 'Starting Jitsi Automatically' instructions.

Once done, follow the 'Jitsi Configuration and Bring-Up' instructions next. To get started, first follow 'RPi4 64-bit Gentoo Install' instructions below.

#JITSI MEET NGINX INSTALL#

I have built and pushed the necessary binary packages to the binhost, and made required changes to masks etc in the custom profile, so now you can easily install your own Jitsi server instance on an RPi4 running gentoo-on-rpi-64bit! (Of course, you can also build from source if you wish, rather than using the binhost.) A 2GiB RPi4 is realistically the minimum system to use here (NB: because Jitsi does not process the video streams, but acts simply as a meeting coordination point, selective forwarding unit and TURN server, the CPU requirements are not onerous - an RPi4 should be able to handle a reasonable number of simultaneous participants).

#JITSI MEET NGINX PASSWORD#

Starting a new video-conference is set up to require a password by default (and once created, you can then add a password to that particular conference at your option, before distributing the URL to others). Automated TLS certificate issuance (and renewal) via Let's Encrypt is supported, but not mandated. The server-side Java components are built from source (*) using the provided java-maven-pkg eclass. The ebuilds support both OpenRC and systemd, allow for use of either nginx (preferred) or apache as the webserver, and are available on ~amd64 (x86_64) and ~arm64 (aarch64). To help address this, I have recently put together a set of ebuilds in my sakaki-tools overlay which covers the core Jitsi service set, including a pkg_config step that mirrors the flow of upstream's debconf / postinst logic, providing an easy, prompt-based setup for single-box installs. While Debian has a multi-component, debconf-guided solution for this ( curated by upstream), Gentoo currently does not (in tree anyhow). Unfortunately however, setting up your own Jitsi server instance is somewhat complex, due to the requirement to cross-sectionally configure a group of services, integrate with Let's Encrypt (for certificate management) etc. The source is available here, and you can quickly try Jitsi, with no password needed, at

#JITSI MEET NGINX ANDROID#

It has a client that runs purely in your web browser (with native Android and iOS clients also available), coupled with a back-end server complex that performs forum management, selective video forwarding, NAT traversal etc. for video-conferencing, you may have come across Jitsi Meet, an Apache-licensed WebRTC-based solution. If you're looking for a secure, FOSS alternative to Zoom, Hangouts etc.

Jitsi meet nginx