UniversityRadioYork / UniversityRadioYork/WebStudio
Long-term TURN server solution
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The current impl uses a public TURN server with a limited bandwidth. We probably want to run our own - but that involves ITS opening a shit-ton of ports to the outside world. Maybe share it with YSTV, so it's one weird port request not two weird port requests?
The alternative being opening all incoming UDP to Dolby, which is unlikely to happen.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the current public TURN-server configuration and review how it is used by the WebStudio deployment. Clarify the ITS port constraints and whether sharing infrastructure with YSTV is viable; done means an agreed long-term hosting and networking plan is documented and actionable.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100