#Jitsi meet no volume install
They then suggest to install Let’s Encrypt certificate using the script they provide. We’ll refer to the domain name you gave as $HOSTNAME in the following. During the installation you’ll be asked for two things: A domain name under which you want to serve your instance (which you cannot easily change later) and whether you want to use existing certificates. You need to follow the linked Quick Install document up to the point where apt install jitsi-meet is called. Though if you go with Docker, you may be interested in docker-jitsi-meet instead. If you, like me, do not like enabling third-party repositories on productive servers, I suggest you put your Jitsi instance in an LXC-based container. To install Jitsi Meet on Debian, you first have to enable the apt repository by the Jitsi developers. Six people, seven Jitsi Meet clients, five hours. In the second part of the post I will present some measurements I took during our pen&paper session last night. I only deployed mumble as a fail-safe fallback option, which we luckily did not need. A few, because for one it is super easy to set up, but also because it is audio-only. In addition, I’ll say a few words about Mumble.
In the first part, this post will describe how I set up jitsi-meet on my own server.
While it has been long on my to do list to implement one of the various standards which exist around the real-time transmission of audio and video data, I never got around to do it. I am active in the instant messaging standards community, however, I have never really delved into A/V conferencing. In order to still be able to continue the story and get some social interaction, a solution had to be found. It can be a very fun activity, but the isolation rules which have been put in place (rightfully!) rule out physically meeting up with each other.
That means we meet every week for an evening to basically tell a story together, with some rules. My wife and I have a pen&paper group (let’s get this out of the way).
0 kommentar(er)
