Briq
/
multiparty-meeting
7
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Fork of github.com/havfo/multiparty-meeting
179 Commits
4 Branches
0 Tags
8.5 MiB
JavaScript 97.8%
RPM Spec 1.1%
Shell 0.4%
Dockerfile 0.3%
CSS 0.2%
Other 0.2%
 
 
 
 
 
 
Go to file
Torjus 02099054b3 Merge branch 'develop' of github.com:havfo/multiparty-meeting into feat/chat-images 
* 'develop' of github.com:havfo/multiparty-meeting:
  fix: unread badge is number not bool
  Just to make toolarea a little bit less ugly
  microphone indicator changes opacity with volume level
  hark running now on producers and consumers directly instead on PeerView component, now we can send audiolevel events into more places ...
  Fix fade-out animation running on page load
 		2018-07-18 14:52:31 +02:00
app Consistent avatar styling in chat and users tabs 2018-07-18 14:46:19 +02:00
server Merge develop and remove comments 2018-07-18 14:45:36 +02:00
.gitignore Preparation for Chrome screen sharing plugin. 2018-03-04 12:49:08 +01:00
README.md Cleaned up naming. Removed node-random-name to reduce size of final JS with about 50%. Updated README. 2018-03-03 13:27:02 +01:00
multiparty-meeting.service adding service file for systemd for automatical upstart of the service: this makes sense in future when the server hosts his own static files by himself 2018-06-05 17:25:02 +02:00

README.md

multiparty-meeting

A WebRTC meeting service using mediasoup as its backend.

Try it online at https://mediasoup.akademia.no.

Installation

  • Clone the project:
$ git clone https://github.com/havfo/multiparty-meeting.git
$ cd multiparty-meeting
  • Set up the server:
$ cd server
$ npm install
  • Copy config.example.js as config.js and customize it for your scenario:
$ cp config.example.js config.js
  • Set up the browser app:
$ cd app
$ npm install
  • Globally install gulp-cli NPM module (may need sudo):
$ npm install -g gulp-cli

Run it locally

  • Run the Node.js server application in a terminal:
$ cd server
$ node server.js
  • In another terminal build and run the browser application:
$ cd app
$ gulp live
  • Enjoy.

Deploy it in a server

  • Build the production ready browser application:
$ cd app
$ gulp dist

  • Upload the entire server folder to your server and make your web server (Apache, Nginx...) expose the server/public folder.

  • Edit your server/config.js with appropriate settings (listening IP/port, logging options, valid TLS certificate, etc).

  • Within your server, run the server side Node.js application. We recommend using the pm2 NPM daemon launcher, but any other can be used.

Author

  • Håvar Aambø Fosstveit

This is heavily based on the work done by:

License

MIT