[jitsi-users] jitsi-meet with ejabberd/Apache


#1

Hi there,

I'm a little bit confused, the debian-package for jitsi-meet depends on
propsody and ngnix ?

Depends: debconf (>= 0.5) | debconf-2.0, jitsi-videobridge,
jitsi-meet-prosody, libjs-jquery, libjs-jquery-ui,
openjdk-8-jre-headless | nginx

That means it is not possible to run jitsi-meet with ejabberd and apache
? Or did I choose the wrong package ?

Any hint/help appreciated...

Regards
Peter


#2

No, it just means that the deb packages that are available depend on
nginx and prosody.

If you don't have other reason to use a different web and xmpp server,
nginx and prosody work really well. On a newer install with openjdk-8
available you can omit the nginx dependency and rely on jetty -- it's
the default setup for new installs with openjdk-8.

There are no other packages, but you can always reconfigure the server
to use apache and/or ejabberd|openfire etc. Some people are using such
setups with apache and openfire, but YMMV, as the upstream tested
setup is nginx|jetty and prosody.

···

On Thu, 01 Oct 2015 12:16:50 +0200 Peter Beck wrote:

I'm a little bit confused, the debian-package for jitsi-meet depends on
propsody and ngnix ?

Depends: debconf (>= 0.5) | debconf-2.0, jitsi-videobridge,
jitsi-meet-prosody, libjs-jquery, libjs-jquery-ui,
openjdk-8-jre-headless | nginx

That means it is not possible to run jitsi-meet with ejabberd and
apache ? Or did I choose the wrong package ?

--

Yasen Pramatarov
Lindeas Ltd. https://lindeas.com
'working on GNU/Linux ideas'
Professional Jitsi Meet services


#3

Hi Yasen,

thanks for clarification. I'm also very pleased with ejabberd, running a
few ejabberd-servers without any hassle, they just run and run...
And I am also more convenient using Apache as this is the webserver I
know and I'm also very pleased with.

So that means I'll have to add jessie-backports (for openjdk-8) and then
just modify (change dependencies) and rebuild the package and I am good
to go ? Or can I even run jitsi-meet with openjdk-7 (which is in the
main jessie repository) ?

Regards
Peter

···

On 10/01/2015 12:36 PM, Yasen Pramatarov wrote:

No, it just means that the deb packages that are available depend on
nginx and prosody.

If you don't have other reason to use a different web and xmpp server,
nginx and prosody work really well. On a newer install with openjdk-8
available you can omit the nginx dependency and rely on jetty -- it's
the default setup for new installs with openjdk-8.

There are no other packages, but you can always reconfigure the server
to use apache and/or ejabberd|openfire etc. Some people are using such
setups with apache and openfire, but YMMV, as the upstream tested
setup is nginx|jetty and prosody.


#4

I mentioned openjdk-8 only when referring to jetty configs in the
packages. It's not related to Apache, except for replacing it in some
configs. Still, have in mind that if you go for jetty it will listen
on port 443 only and you will need some other way (web server or
iptables) to redirect 80 to 443.

If you need Apache, you can configure it on a vanilla Jessie. The
search on internet shows for example this:

http://lists.jitsi.org/pipermail/dev/2014-February/019946.html

Configuration of a different XMPP server is also OK, as long ans the
server supports jabber components (ejabberd surely does, IIRC).

···

On Thu, 01 Oct 2015 12:52:00 +0200 Peter Beck wrote:

So that means I'll have to add jessie-backports (for openjdk-8) and
then just modify (change dependencies) and rebuild the package and I
am good to go ? Or can I even run jitsi-meet with openjdk-7 (which is
in the main jessie repository) ?

--

Yasen Pramatarov
Lindeas Ltd. https://lindeas.com
'working on GNU/Linux ideas'
Professional Jitsi Meet services


#5

One more thing, tweaking only the package dependencies won't do much,
as the postinst/postrm scripts do a lot of nginx and prosody
configuration.

So if you tweak the dependencies, you will either have no
configurations (virtual hosts, components etc.) and you will have to
do all manually for apache and ejabberd or you will end up with broken
packages if the postinst scripts fail with a message.

It's all doable, but you have to keep an eye for errors.

If you want to use the packages you have to clear the packages scripts
content too, along with the dependencies. And after that do the configs
manually.

Or you can edit the scripts to add support for apache/ejabberd.

···

On Thu, 01 Oct 2015 12:52:00 +0200 Peter Beck wrote:

So that means I'll have to add jessie-backports (for openjdk-8) and
then just modify (change dependencies) and rebuild the package and I
am good to go ?

--

Yasen Pramatarov
Lindeas Ltd. https://lindeas.com
'working on GNU/Linux ideas'
Professional Jitsi Meet services