[jitsi-dev] jitsi-meet depends on prosody?


#1

Hi,

I just had some trouble installing jitsi-videobridge and jitsi-meet
from the ubuntu-package provided by jitsi, because jitsi-meet depends
on jitsi-meet-prosody, and jitsi-meet-prosody depends on prosody, thus
the presence of prosody is enforced.

I wanted to install this with ejabberd, and the docs for
jitsi-videobridge contain details about configuring ejabberd, so it is
supported.

Furthermore and as far as I understand (and supported by the graphics
under
https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md

jitsi-meet should be a web/js application and not bound to a
particular jabber server.

I found that ejabberd could not start since the ports were already
occupied by prosody, and I am wondering why jitsi-meet does enforce
prosody, while jitsi-meet is independent of a jabber server and
jitsi-videobridge is said to cope with ejabberd as well.

best regards
Hadmut


#2

Hi,

The package you install jitsi-meet is a meta package and consist of
various components in order for users to install using a single
command and at the end have a working conference solution. These
dependencies consist of a web application, a way to serve it nginx,
apache2 or jetty from jvb, a video bridge, a controlling component
called jicofo and a XMPP server that connects them all which we chose
back in time and is prosody.
If you want to customize this solution you can install separate
packages and configure them one by one. You can use your web server
and your XMPP server and install just jitsi-meet-web,
jitsi-videobridge and jicofo.
A PR for configuring different XMPP servers in the system is welcome.

Regards
damencho

ยทยทยท

On Thu, Apr 6, 2017 at 10:15 AM, Hadmut Danisch <hadmut@danisch.de> wrote:

Hi,

I just had some trouble installing jitsi-videobridge and jitsi-meet
from the ubuntu-package provided by jitsi, because jitsi-meet depends
on jitsi-meet-prosody, and jitsi-meet-prosody depends on prosody, thus
the presence of prosody is enforced.

I wanted to install this with ejabberd, and the docs for
jitsi-videobridge contain details about configuring ejabberd, so it is
supported.

Furthermore and as far as I understand (and supported by the graphics
under
https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md

jitsi-meet should be a web/js application and not bound to a
particular jabber server.

I found that ejabberd could not start since the ports were already
occupied by prosody, and I am wondering why jitsi-meet does enforce
prosody, while jitsi-meet is independent of a jabber server and
jitsi-videobridge is said to cope with ejabberd as well.

best regards
Hadmut

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev