You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Paul Tirk f21360c58f add more eslint rules 1 year ago
docker Add Docker Compose support 1 year ago
src export types in type definition files 1 year ago
.eslintrc.json add more eslint rules 1 year ago
.gitignore first commit 1 year ago
.gitlab-ci.yml only lint source folder in .gitlab-ci.yml 1 year ago
LICENSE add LICENSE 1 year ago
README.md Merge branch 'enh/noid/docker-compose' into 'master' 1 year ago
config.json first commit 1 year ago
docker-compose.yml Add Docker Compose support 1 year ago
package-lock.json extend package.json, add tags to docker commands & add some types 1 year ago
package.json extend package.json, add tags to docker commands & add some types 1 year ago
tsconfig.json add more linter rules & lint 1 year ago
webpack.config.js Add Docker Compose support 1 year ago

README.md

Nextcloud Talk Backend

Important: This project is not finished and still not working very well. It is supposed to be a proof-of-concept and not (yet) stable enough to be used in production environments!

Since the default internal signaling was not usable on my system and Nextcloud's own High-Performance-Backend is not affordable by private users, I decided to take a shot and implement a signaling server based on what can be found in the source of Nextcloud Talk and the API documentation.

Signaling Server

The signaling server itself communicates over a WebSocket connection. For better performance it is recommended to use a separate MCU/SFU. I worked with Janus but I try to keep the interface abstract so it should be possible to expand the connectors for using other servers (Jitsi, etc.)

How to run

Docker

There is a pre-made docker-compose.yml. Modify the environment variables in the file to your needs then run the following commands:

docker-compose build
docker-compose up -d