deploy own PeerServer?
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
this client is pretty functional, but i often get `Error: Server has reached its concurrent user limit`.
the signaling server is [used for finding one another](https://webrtcforthecurious.com/docs/02-signaling/), but i don't fully understand how long one occupies space on the server. maybe my use of the server could be better, but it doesn't really matter if lots of others are using it too.
looks like it should be easy to deploy another: https://github.com/peers/peerjs-server
Contributor guide
No contributing guide indexed for this repository
Research direction
Review how the JavaScript client currently selects or connects to its signaling server, then read the linked PeerJS server project for deployment requirements. Done means the project has a documented or working alternative PeerServer setup and the client can connect through it without hitting the shared server limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100