<a href="https://travis-ci.org/socketio/socket.io-redis"><img src="https://travis-ci.org/socketio/socket.io-redis.svg?branch=master" /></a> <a href="http://badge.fury.io/js/socket.io-redis"><img src="https://badge.fury.io/js/socket.io-redis.svg" /></a>
var io = 3000;var redis = ;io;
By running socket.io with the
socket.io-redis adapter you can run
multiple socket.io instances in different processes or servers that can
all broadcast and emit events to and from each other.
If you need to emit events to socket.io instances from a non-socket.io process, you should use socket.io-emitter.
uri is a string like
localhost:6379 where your redis server
is located. For a list of options see below.
The following options are allowed:
key: the name of the key to pub/sub events on as prefix (
host: host to connect to redis on (
port: port to connect to redis on (
pubClient: optional, the redis client to publish events on
subClient: optional, the redis client to subscribe to events on
If you decide to supply
subClient, make sure you use
node_redis as a client or one
with an equivalent API.
If you supply clients, make sure you initialized them with
return_buffers option set to
The redis adapter instances expose the following properties
that a regular
Adapter does not
subClient properties of the
Redis Adapter instance to subscribe to its
var redis = ;var adapter = ;adapterpubClient;adaptersubClient;
If you need to create a redisAdapter to a redis instance that has a password, use pub/sub options instead of passing a connection string.
var redis = createClient;var adapter = ;var pub = ;var sub = ;io;
Make sure the
return_buffers option is set to
true for the sub client.