Mooz

WebRTC based video chat app whose name and other stuff is 100% orignal. I would write some sexy and sophisticated line, but I have lost it.

Demo

TODO A good-looking gif

Uses

React my love.
Socketio for signaling and room management. I don't use REST and Express at all in this, sue me.
Fluentui for good-looking UI components without writing much CSS and therefore less hairfall.
Recoil for local state management, fuck Redux.

Pretty known thing for peer-to-peer WebRTC connections but I will still state this for commercial purposes: All connection data like video, audio and messages are tranfered peer to peer without going through server.

Goal

Open source peer-to-peer video conferencing app core, easily deployable and extendable for custom use cases. So instead of everyone creating those ugly video chat apps, this can be extended for any extra custom features like, file sharing, session recording, options for Media server based solution and/or encryption, etc.

Limitations

It scales very well in terms of how many rooms can be on server as it is a peer to peer solution, infact a peer doesn't even need to be connected to server once connection is esablished with other peer. However there is a huge natural limitation on how many participants can be in one single room due to bandwidth and processing requirements. Peer-to-peer playes negative role on that front as every peer is sending and recieving data with every peer in a room. This limitation is little overcomed with adaptive bandwidth usage and other optimizations, but core limitation is by design.

Why node-cache instead of database?

Works for now

TODO migrate to redis adapter.

Deploying

Prebuilt images with docker-compose

Run the provided docker-compose file in appropriate place

docker-compose up

And done, just serve behind ssl, expose port 5000 for sockets and enjoy your life. If you want to deploy modified app, see options below.

TODO proxy websockets with nginx without having to open port.

Docker

This project is split into two containers, one for react front-end which is build and then served with nginx and other for server.

Build images

Following commands builds these images respectively.

cd %project-root%

docker build --build-arg SOCKET_PORT=5000 --tag mooz .

docker build --tag mooz-server ./server

Run containers

docker run -d --rm -p 80:80 --name client mooz

docker run -d --rm -p 5000:5000 -e "PORT=5000" --name server mooz-server

If you are gonna have server and client on different domains, pass ALLOW_ORIGIN env varibale to server and REACT_APP_SOCKET_URL to client.

Manual

If you dont wan't to use docker, these are the npm commands for every step.

[cd ]

npm install to to install react dependencies.

npm run dev to start development webpack server.

npm run build to format, lint and build front-end.

Then serve static files accordingly

[cd server]

npm install installs Server dependencies.

npm run dev to start development server with nodemon (install globally).

npm run build transpiles Typescript server file to JavaScript.

npm run start starts the Node/Scoket.io server.

Get a life dude!

Still reading? Woowowowoow.

erohin/mooz