Jerko Steiner aa2f3f47d8 Fix a bug introduced by SocketIO not having consistent ids
During the time of the initial release of Peer Calls, the server and
client sockets used to have different namespaces - one side had `/#`
prepended to the name, whereas the other did not, so I had to check for
this in the code.

This was fixed since the release of [SocketIO v1.5.0][1], thus breaking the
compatibility with PeerCalls. Any new `npm install` would break this
because of the way it works - it tries to install the latest available
"compatible" release.

As of this commit, the SocketIO version is locked to v1.6.0.

[1]: https://github.com/socketio/socket.io/releases/tag/1.5.0
2016-11-22 11:10:08 -05:00
2016-03-31 18:40:47 -04:00
2016-04-04 18:01:31 -04:00
2016-04-03 13:18:58 -04:00
2016-04-06 20:44:12 -04:00
2016-04-24 14:48:07 -04:00
2016-04-04 18:35:13 -04:00

Peer Calls

Build Status

WebRTC peer to peer calls for everyone. See it live in action at peercalls.com.

Work in progress.

Requirements

Installation & Running

From git source:

git clone https://github.com/jeremija/peer-calls.git
cd peer-calls
npm install
npm start

If you successfully completed the above steps, your commandline/terminal should show that your node server is listening.

On your other machine or mobile device open the url:

http://<your_ip_or_localhost>:3000

(Note: On Android you may have to select a notification on the pulldown menu to connect if you are using Chrome)

Testing

npm install
npm test

Contributing

See Contributing section.

License

MIT

Description
No description provided
Readme 4 MiB
Languages
TypeScript 88.9%
SCSS 9.3%
HTML 1.1%
JavaScript 0.4%
Dockerfile 0.3%