Package Details: jitsi-meet-git r7978.e0d41a30e-1

Git Clone URL: (read-only, click to copy)
Package Base: jitsi-meet-git
Description: WebRTC JavaScript video conferences
Upstream URL:
Licenses: Apache
Conflicts: jitsi-meet
Provides: jitsi-meet
Submitter: C0rn3j
Maintainer: C0rn3j (fordprefect)
Last Packager: C0rn3j
Votes: 1
Popularity: 0.000942
First Submitted: 2020-03-14 16:12
Last Updated: 2020-11-22 15:38

Latest Comments

celogeek commented on 2020-05-27 00:27


this package is made to develop on jitsi-meet? or to get the latest updated version from jitsi-meet?

do we need to have the development and the resource files in the install repository? (node_modules, .git, lua scripts, ...)

if not, may be you can do a "make source-package" at the end of the installation and deploy only that?

why using /opt instead of /usr/share/jitsi-meet ?

This package provide the same feature, and if an user want to go from stable to git package, it doesn't have to reconfigure prosody/nginx/config?

can we also have config in the same place as the other package, in /etc/jitsi/meet?

this ease a lot the migration from one version to another.

danieltetraquark commented on 2020-04-21 13:59

I think it would be good idea to symlink the config files to /etc/webapps/jitsi-meet

C0rn3j commented on 2020-04-15 20:18

@buzo Thanks, fixed it!

buzo commented on 2020-04-15 19:45

Since this is a git package, it should contain a pkgver() function, see here. Could you please add it?

tinux commented on 2020-04-02 12:36

Thanks a lot!! I'll try my luck tonight.

C0rn3j commented on 2020-04-02 12:29

The manual install guide is already pretty OS agnostic, the only real change you have to make is trusting the certificate, which you can do like so:

trust anchor /var/lib/prosody/

Do note that my packages (jitsi-meet-git, jitsi-videobridge, jicofo-git) currently use different configuration paths/service from the other packager(jitsi-meet-bin, jitsi-videbridge-bin, jicofo-bin), so read the PKGBUILD and the source files.

Here's my older notes - you can ignore the multi-sharp comments as they're handled by the packages.

And the used files are here

tinux commented on 2020-04-02 12:12

Am I assuming correctly, that this is what you're using to configure jitsi on your arch systems? Is anyone aware of arch-specific installation instructions? Thanks