No Description

Eden Tyler-Moss e5c7ab517f Fixed bug where using the original randomId function would break. 5 years ago
bin 799299d669 add checkConnections service 6 years ago
config 799299d669 add checkConnections service 6 years ago
src e5c7ab517f Fixed bug where using the original randomId function would break. 5 years ago
test 799299d669 add checkConnections service 6 years ago
.eslintrc.json 252b65cc07 add eslint 6 years ago
.gitignore 9c789f96b5 Updated dependencies. 7 years ago
.travis.yml 1e09fcfb64 ref 6 years ago
Dockerfile ecd849f246 fix docker file 6 years ago
LICENSE b8dbd1f249 license and updated package json 12 years ago
README.md ae5452b2e1 Update README.md 5 years ago
app.json bd101ab44f enable "Deploy to Heroku" Button 10 years ago
changelog.md 8bfd385eb0 add 0.3.0 section to changelog 6 years ago
package-lock.json 8c00c0decd update deps 6 years ago
package.json 94616d6e35 enabled support for node.js engines > 10 5 years ago

README.md

Build Status

PeerServer: A server for PeerJS

This fork of peerjs-server adds functionality to set a custom ID generation fucntion. Commit

PeerServer helps broker connections between PeerJS clients. Data is not proxied through the server.

https://peerjs.com

Run PeerServer

  1. Clone app:

    git clone https://github.com/peers/peerjs-server.git
    
  2. Install dependencies:

    npm install
    
  3. Run the server:

    $> peerjs --port 9000 --key peerjs --path /myapp
    

Or, create a custom server:

$> npm install peerjs-server
import {PeerServer} from 'peerjs-server';

const server = PeerServer({port: 9000, path: '/myapp'});

Connecting to the server from PeerJS:

<script>
    const peer = new Peer('someid', {host: 'localhost', port: 9000, path: '/myapp'});
</script>

Using HTTPS: Simply pass in PEM-encoded certificate and key.

import fs from 'fs';
import {PeerServer} from 'peerjs-server';

const server = PeerServer({
  port: 9000,
  ssl: {
    key: fs.readFileSync('/path/to/your/ssl/key/here.key'),
    cert: fs.readFileSync('/path/to/your/ssl/certificate/here.crt')
  }
});

Running PeerServer behind a reverse proxy

Make sure to set the proxied option, otherwise IP based limiting will fail. The option is passed verbatim to the expressjs trust proxy setting if it is truthy.

import {PeerServer} from 'peerjs-server';

const server = PeerServer({port: 9000, path: '/myapp', proxied: true});

Combining with existing express app

import express from 'express';
import {ExpressPeerServer} from 'peerjs-server';

const app = express();
app.get('/', (req, res, next) => { res.send('Hello world!'); });

// =======

const server = app.listen(9000);

const options = {
    debug: true
}

const peerserver = ExpressPeerServer(server, options);

app.use('/api', peerserver);

// == OR ==

import http from 'http';

const server = http.createServer(app);
const peerserver = ExpressPeerServer(server, options);

app.use('/peerjs', peerserver);

server.listen(9000);

// ========

Events

The 'connection' event is emitted when a peer connects to the server.

peerserver.on('connection', (client) => { ... });

The 'disconnect' event is emitted when a peer disconnects from the server or when the peer can no longer be reached.

peerserver.on('disconnect', (client) => { ... });

Running tests

npm test

Docker

You can build this image simply by calling:

docker build -t peerjs https://github.com/peers/peerjs-server.git

To run the image execute this:

docker run -p 9000:9000 -d peerjs

This will start a peerjs server on port 9000 exposed on port 9000.

Problems?

Discuss PeerJS on our Google Group: https://groups.google.com/forum/?fromgroups#!forum/peerjs

Please post any bugs as a Github issue.