NC TURN Server now an automated install

[ei8fdb]

Hi all,

The Nextcloud Talk Signaling Server can now be installed in the Nextcloud VM 17. They've made the setup is totally automated.

You can read it here: https://help.nextcloud.com/t/nextcloud-talk-signaling-server-now-automated-installation/90567

I'm guessing it's possible to run this straight in a Cloudron VM? Thanks!

[girish]

@ei8fdb Cloudron already has a built-in turn server that is shared across apps (for example, kopano meet etc). You can see TURN service listed under the Services view. The nextcloud app is already pre-configured to use the build-in turn service.

[oj]

@girish I think what @ei8fdb trying to say (via the link that he has inserted) is that the Nextcloud VM folk now have an automated installation available for the High Performance Backend (Signalling Server + Janus SFU) of Nextcloud Talk.

[girish]

Ah sorry, I misread his post. That is indeed nice and we should look into integrating it into Cloudron.

[jdaviescoates]

@oj said in NC TURN Server now an automated install:

@girish I think what @ei8fdb trying to say (via the link that he has inserted) is that the Nextcloud VM folk now have an automated installation available for the High Performance Backend (Signalling Server + Janus SFU) of Nextcloud Talk.

I'm not sure, doesn't look like this includes Janus SFU, just the signalling server.

I'd love Cloudron to have the full High Performance Backend though!

[girish]

I wasn't aware that the signaling server is now open source - https://github.com/strukturag/nextcloud-spreed-signaling

@jdaviescoates It seems Janus and HPB are indeed installed. Further down in the code at https://github.com/nextcloud/vm/blob/master/apps/talk_signaling.sh#L272

[jdaviescoates]

@girish aha, great! @doodlemania2 has been doing some work packaging the HPB and I guess this might help with that then?

[doodlemania2]

@jdaviescoates would love assistance! am currently waiting on the TURN addon in CR to support API authentication (where I'm currently blocked). There are scads of other improvements I've not even started on if you'd like to take a swing at it - my alpha testing was to just get it to run. Am able to do so, but again, needs lots of cleaning (and the TURN stuff).

[jdaviescoates]

@doodlemania2 I can't help myself sorry, not a coder at all

[will]

@girish Off-topic thought:
What if we folded matrix into the system like the turn server? Made it another "service"?

[girish]

@will Usually, we make something a service if it's shared by many apps or can be used by many apps. I think it would make sense to make matrix as a service if many more apps use the same communication protocol backend. AFAIK, right now, we only have Element.

[ei8fdb]

What is the best thing for me to do here? Should I make an app request for Nextcloud's Turn server?

[girish]

@ei8fdb I think the app request is to package nextcloud's high performance backend and not the TURN server. IIRC, it is/was opensource but I cannot find the github repo link anymore.

[girish]

i think maybe it's this one - https://github.com/strukturag/nextcloud-spreed-signaling

[jdaviescoates]

@girish yep, that's the one.

Here's the app request:
https://forum.cloudron.io/post/8642

[ei8fdb]

@jdaviescoates Ah already done. Upvoted then. Thanks