INACTIVE - http://mzl.la/ghe-archive - Signaling server to connect pairs of WebRTC clients
Перейти к файлу
Kian Solomon bb59a2fca7 updated readme 2017-01-17 08:49:46 -08:00
.gitignore Ignore .keys directory 2016-11-14 13:38:24 -08:00
README.md updated readme 2017-01-17 08:49:46 -08:00
index.js error handling fixed 2016-12-01 14:13:02 -08:00
package.json Just generate a single key pair using a HAIKU_DEVICE_ID environment variable in the filename 2016-11-14 13:36:14 -08:00
rsa-keypairgen.js Just generate a single key pair using a HAIKU_DEVICE_ID environment variable in the filename 2016-11-14 13:36:14 -08:00

README.md

##Project Haiku WebRTC Signaling Server

###Project Status - On Hold

The current status of the project due to resource constraints is On Hold. We are archiving and keeping [log of the work here] (https://github.com/mozilla/project_haiku.iot/wiki/Useful-Links-and-Work-Log).

###Install:

npm install

###There are two ways to authenticate and create a peer-to-peer connection using this signaling server: ####The instructions below are how to connect your client from this repo: https://github.com/sfoster/webrtc-datachannel-test

###Before you do anything, you have to generate the public Private Key pairs: - Navigate into the node-client folder. - Run node rsa-keypairgen.js - Now you should have a .keys folder containing node-client-a.pub.pem & node-client-a.pem - In order to authenticate & connect to the signaling server, the server needs your node-client-a.pub.pem and you need the servers signaling_server.pub.pem

###Then to run the node-client (not CLI): - Navigate into the node-client folder. - Make sure you have a .keys file with node-client-a.pem and signaling_server.pub.pem (check above) - Make sure the server has the up to date node-client-a.pub.pem key - Run node index.js - ...