Nextcloud Talk high-performance back-end
-
Yeah, sorry, I meant that signaling would be externally accessible, but it appears nats and janus do not as signaling just calls them. Does that sound about right or am I WAY off?
-
Continuing to play with this. I think it's working, but I think more than just the signaling app needs access to the internet. I think the Janus bits need to be accessible as well. Currently, it's behind the docker net.
-
Going to build Janus and dependencies from source (which will take some time) as the backports are old. While doing this, @nebulon is working on an update to TURN/STUN to enable API access in CR itself! See: https://git.cloudron.io/cloudron/box/-/issues/710
-
@doodlemania2 have you managed to make any further progress with getting this packaged? Thanks!
-
Hi @jdaviescoates - yep - we need to wait for an update to Box to support Auth API things on the Turn server. cc: @girish
-
@jdaviescoates said in Nextcloud Talk high-performance back-end:
Sounds tantalisingly close, thanks @doodlemania2 @girish !
In the meantime, Nextcloud 20 is going to make it easy to sign-up to a hosted Nextcloud High Performance Backend
See:
https://nextcloud.com/press/pr20201003-6/
https://help.nextcloud.com/t/nextcloud-hub-20-debuts-dashboard-unifies-search-and-notifications-integrates-with-other-technologies/93838
https://www.spreed.eu/contact-nextcloud-talk-high-performance-backend/ -
I've got a very early prototype of this working - it just needs some API fun from the Cloudron TURN feature sets. https://git.cloudron.io/doodlemania2/nthpbe
-
Exciting, thanks @doodlemania2!
-
@doodlemania2 You might be interested in this: Nextcloud Talk High Performance Backend with Stun/Turnserver on Ubuntu with docker-compose
-
@doodlemania2 To continue the discussion from the other thread about the TURN server requirements.
Per https://markus-blog.de/index.php/2020/07/30/how-to-install-nextcloud-talk-high-performance-backend-with-stun-turnserver-on-ubuntu/, the turnserver only requires a static-auth-secret and that is already set in existing turn server. I guess you are referring to the
turn_rest_api_keyin the janus configs? That secret is generated and shared between janus and nextcloud-spreed-signaling server from what I can understand. I think the existing turn service should work as-is. -
@doodlemania2 said in Nextcloud Talk high-performance back-end:
okay - let me re-start my efforts and will study it more closely in addition to @oj 's and others suggestions to look at a prebuilt docker for inspiration.
Did you manage to have another look? Would be so great to have this!
-
@jdaviescoates
I haven't yet and I feel really bad about it - work has been all consuming of late. It's literally at the top of my list, just haven't had a chance! I promise more soon fast as I can! -
@doodlemania2 don't feel bad about it!
But also, great, thanks!
-
@jdaviescoates I've been trying to get this to work but it just doesn't (based on the docker-compose example). I've reached out to the author of the blog to see if he can assist!
-
this is ready for testing - please send me a DM if you'd like to try it out!
-
@doodlemania2 great news! Is https://git.cloudron.io/doodlemania2/nthpbe still the latest repo because it says the commits are from 9 months ago.
-
@girish we can delete that repo actually - instead of creating a fully packaged cloudron custom app, I decided to offer this to the cloudron community for free* from my VPSs.
*standard "be nice folks" or I turn it off
