Complete documentation available at: http://socketcluster.io/
Documentation for SCC is available at https://github.com/SocketCluster/socketcluster/blob/master/scc-guide.md
SocketCluster is a fast, highly scalable HTTP + realtime server engine which lets you build multi-process realtime servers that make use of all CPU cores on a machine/instance. It removes the limitations of having to run your Node.js server as a single thread and makes your backend resilient by automatically recovering from worker crashes and aggregating errors into a central log on each host. SC can also auto-scale across multiple hosts on top of Kubernetes; see SCC guide: https://github.com/SocketCluster/socketcluster/blob/master/scc-guide.md.
There are two ways to install SocketCluster.
The easy way (Sets up boilerplate - Ready to run):
Setup the socketcluster command:
npm install -g socketcluster
sudo npm install -g socketcluster
socketcluster create myapp
Once it's installed, go to your new myapp/ directory and launch with:
Access at URL http://localhost:8000/
The hard way (More modular - Separate server and client):
npm install socketcluster
You will also need to install the client separately which you can get using the following command:
npm install socketcluster-client
The socketcluster-client script is called socketcluster.js (located in the main socketcluster-client directory)
- You should include it in your HTML page using a <script> tag in order to interact with SocketCluster. For more details on how to use socketcluster-client, go to https://github.com/SocketCluster/socketcluster-client
It is recommended that you use Node.js version >=0.10.22 due to memory leaks present in older versions.
Using over HTTPS
In order to run SocketCluster over HTTPS, all you need to do is set the protocol to 'https' and provide your private key and certificate as a start option when you instantiate SocketCluster - Example:
var socketCluster =workers: 3brokers: 3port: 8000appName: 'myapp'workerController: 'worker.js'protocol: 'https'protocolOptions:key: fscert: fspassphrase: 'passphase4privkey';
The protocolOptions option is exactly the same as the one you pass to a standard Node HTTPS server: http://nodejs.org/api/https.html#https_https_createserver_options_requestlistener
Docker and SocketCluster
You can create an app on top of SocketCluster's docker image. The SC container can be run standalone or as a base image for your own container.
The official SocketCluster container on DockerHub is here: https://hub.docker.com/r/socketcluster/socketcluster/
The Dockerfile for the base image is here: https://github.com/SocketCluster/socketcluster/blob/master/sample/Dockerfile
To use the SocketCluster container as your base image, your app's Dockerfile might look like this:
FROM socketcluster/socketcluster MAINTAINER John Smith LABEL version="1.0.0" LABEL description="Custom app based on SocketCluster" WORKDIR /usr/src/ COPY . /usr/src/ RUN npm install EXPOSE 8000 CMD ["npm", "start"]
Then you can just build your container using:
docker build -t my-socketcluster-app:v1.0.0 .
Note that there are more ways to run SocketCluster with Docker. You can also mount your own volumes and point to custom worker.js and broker.js files which are inside those volumes using environment variables. You can see the environment variables which are used by SocketCluster here: https://github.com/SocketCluster/socketcluster/blob/master/sample/server.js
Docker volumes allow you to sneak your own directories (containing your own worker.js and broker.js source files) into the SocketCluster container without having to rebuild the image (good for development). Read this section on volumes to get an idea of how they work with Docker: https://docs.docker.com/engine/userguide/containers/dockervolumes/
Note that if you want to attach any volumes to your SocketCluster container, you should mount them to the
/usr/src/ path (inside the container) - That's the root directory from which SC loads user-defined source code.
For example, if you wanted to quickly run SocketCluster with your own workerController file (
worker.js), you could just put your
worker.js file inside a
/home/my-username/controllers/ directory (on your host system) and then bundle it into the container as a volume by running a command like this (example):
docker run -d -v /home/my-username/controllers/:/usr/src/controllers/ -p 8000:8000 -e "SOCKETCLUSTER_WORKER_CONTROLLER=/usr/src/controllers/worker.js" socketcluster/socketcluster
-dflag just tells Docker to run the container in the background.
-vflag tells docker to mount the
/home/my-username/controllers/directory (which is on your host machine) and map it to the
/usr/src/controllers/(inside the SocketCluster container).
-eflag allows you to define custom environment variables. Here we are just using the SOCKETCLUSTER_WORKER_CONTROLLER env var to tell SocketCluster to use the worker.js file which is inside the volume which we just mounted to the container at path
- The final argument
socketcluster/socketclusteris the Docker image.
Contribute to SocketCluster
- More integration test cases needed
- Unit tests
- Efficiency/speed - faster is better!
To contribute; clone this repo, then cd inside it and then run npm install to install all dependencies.
If you would like to contribute to the SocketCluster project financially, you can make a Bitcoin donation to the following wallet address:
See GitHub releases for changes.
Search for 'setCodecEngine' in http://socketcluster.io/#!/docs/api-scserver and 'codecEngine' in http://socketcluster.io/#!/docs/api-socketcluster-client for more details.