The quick install works really good and is very nicely documented! Lots of people are setting up Jitsi instance now on VPS and many of them are no experts but just do it since the need arises to have more instances. ![]() I would like to second that it would be awesome to have some short doc on things one can do to improve chat-quality on a server. show originalįirst of all: Thank you so much for the hard work you put into all of this especially at the moment! It is so good to have Jitsi as a tool that enables so many people to continue to be in touch and keep doing the work (e.g. Then add the same FQDN in the `/etc/hosts` file, associating it with the loopback address: If the machine used to host the Jitsi Meet instance has a FQDN (for example ``) already set up in DNS, `/etc/hostname` must contain this FQDN if this is not the case yet, (). # Set up the Fully Qualified Domain Name (FQDN) (optional) If you are logged in using a regular user account, you may need to temporarily increase your permissions (for example, by using `sudo` for individual commands). _Note_: Many of the installation steps require elevated privileges. To ensure this is enabled, run `apt-add-repository universe` at the command-line. On Ubuntu systems, Jitsi requires dependencies from Ubuntu's `universe` package repository. ![]() Debian 9 (Stretch) or later, and Ubuntu 18.04 (Bionic Beaver) or later are supported out-of-the-box. This document describes the required steps for a quick Jitsi Meet installation on a Debian based GNU/Linux system. If you want to have a video conference without setting up any infrastructure, use instead. This guide helps you _host your own Jitsi server_. Intent:// /Riunione_xxyy#jitsi_meet_external_api_id=0&faultLanguage=%22it%22&config.startWithVideoMuted=true&config.startAudioMuted=100&interfaceConfig.DEFAULT_REMOTE_DISPLAY_NAME=%22Partecipante%22&interfaceConfig.TOOLBAR_BUTTONS=%5B%22microphone%22%2C%22camera%22%2C%22closedcaptions%22%2C%22desktop%22%2C%22fullscreen%22%2C%22fodeviceselection%22%2C%22hangup%22%2C%22profile%22%2C%22chat%22%2C%22etherpad%22%2C%22settings%22%2C%22raisehand%22%2C%22videoquality%22%2C%22filmstrip%22%2C%22shortcuts%22%2C%22tileview%22%2C%22download%22%2C%22help%22%5D&interfaceConfig.SETTINGS_SECTIONS=%5B%22devices%22%2C%22language%22%5D&interfaceConfig.TOOLBAR_ALWAYS_VISIBLE=true&userInfo.displayName=%22Marco%20Rivo%22&userInfo.email=%22marco.rixy123%%22#Intent scheme= package= this what you are looking for? jitsi/jitsi-meet/blob/master/doc/quick-install.md # Jitsi Meet quick install However when the App start the connection the displayName is generic: “Partecipant”. It shows the link to open the Jitsi Meet App and in the url I see my configuration (below). Jitsi Meet tells that to partecipate I have to download and use the App. I access the web page with the above configuration with Chrome for Android. In addition the setting TOOLBAR_ALWAYS_VISIBLE doesn’t seem to work on desktop browser. For instance, with the android app any user can set a password or make a livestream.Īlso accessing from the app the displayName is not set and user is shown as “Partecipante” (DEFAULT_REMOTE_DISPLAY_NAME) On desktop browsers this setting works fine, however on android accessing the room with the app (following the link go to the app) these settings are not maintained eventhough I see them in the link url. Since the web page is restricited to logged users I can activate different buttons and settings for the different users with variables $owner_buttons and setting_sections: ie only one user can make a livestream set a password, be a moderator or change the profile. ![]() To embed jitsi meet in my web page I use this configuration: api = new JitsiMeetExternalAPI('', )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |