[Pkg-giraffe-discuss] kopano webmeetings and spreedwebrtc

Sat Nov 12 14:16:35 UTC 2016

After some testing I think Kopano webmeetings is using the standard version of spreed WebRTC which is available here:

https://hub.docker.com/r/spreed/webrtc/

https://github.com/strukturag/spreed-webrtc

Which is also available within nextcloud and others.

This is, as far as I understand, available as docker image (which is the one I have tested), for ubuntu and otherwise as sourcecode which, if the same as Kopano, I was able to compile under Centos 7.

Therefore the question is whether you would want to bother to package the spreedwebrtc web meetings service or simply the Kopano webapp plugin that integrates with webapp. This is simply another webapp plugin which I was able to compile with ant as per zarafa original instructions.

What is important is the Kopano spreedwebrtc configuration file as opposed to the standard spreedwebrtc configuration file, without which, the plugin will not work.

Any thoughts let me know.

Marco

-----Original message-----
From: Marco Costantino <marco at advanced-finance.com>
Sent: Friday 11th November 2016 20:45
To: Guido Günther <agx at sigxcpu.org>
Cc: pkg-giraffe-discuss at lists.alioth.debian.org; Carsten Schoenert <c.schoenert at t-online.de>
Subject: Re: [Pkg-giraffe-discuss] kopano plugins

Guido

 After I compiled it on cantos I moved the executable to Debian and it worked within webapp... I still need to double check what I have done to make sure that's indeed the case. 

 What I am considering how is how or whether at all the Spreed webrtc component that Kopano distributed is different from the Spreed webrtc component which is already available as a package for Ubuntu or as docker image from the Spreed company (can't remember the full name). 

 So I may try to see if I can get the standard one to work within webapp, no idea right now. 

 If that does work the question is I suppose whether we should be packaging the Kopano service at all or just take the one provided by Spreed. 

 Clearly the Kopano webapp web meeting plugin does need to be built and packaged as that's Kopano specific but that's just the integration into webapp. I have built it as per zarafa instructions (they are on the web page when it was first relwased) and it works.

 It can be I suppose easily built as part of the webapp built too it's just another ant script as far as I can tell. 

 Note that as I did mention to Carsten I do not have experience in producing Debian packages at all but I can help where I can with other stuff like this. 

 Marco

On 11 November 2016 18:53:22 GMT+00:00, "Guido Günther" <agx at sigxcpu.org> wrote:

Hi,
On Fri, Nov 11, 2016 at 01:22:10PM +0000, Marco Costantino wrote:

 I managed to compile it by renaming the directory:

 kopano-webmeetings-master/src/app/kopano-webmeetings
 to:
  kopano-webmeetings-master/src/app/spreed-webrtc-server
   But only so far on centos 7. I tried on ubuntu and did not quite succeed and not yet on Debian.

 I have not yet tried integrating this with webapp.

 In any case the build script generated by configure is wrong as it refers to an inexistant directory.

Awesome! I've not tried to reproduce this but having things build would be
great. Don't hesitate to paste failure messages maybe one of us sees
something obvious!
Cheers,
 -- Guido

--------------------------------

Pkg-giraffe-discuss mailing list
Pkg-giraffe-discuss at lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-giraffe-discuss <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-giraffe-discuss> 

 -- 
 Sent from my Android device with K-9 Mail. Please excuse my brevity.

_______________________________________________

Pkg-giraffe-discuss mailing list

Pkg-giraffe-discuss at lists.alioth.debian.org

http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-giraffe-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-giraffe-discuss/attachments/20161112/71380a1e/attachment.html>