Prepare a demo for y-redis about y-redis

[sdzhu]

in your y-websocket repo, modify bin/utils.js like this
//use y-redis
const redisConfig = {
host: process.env.REDIS_HOST,
port: process.env.REDIS_PORT,
password: process.env.REDIS_PASSWORD,
db: process.env.REDIS_DB,
keyPrefix: process.env.REDIS_KEY_PREFIIX
}

const rp = new RedisPersistence({redisOpts: redisConfig})
persistence = {
provider: rp,
bindState: async (docName, ydoc) => {
rp.closeDoc(docName)
return rp.bindState(docName, ydoc)
},
writeState: async (docName, ydoc) => {}
}

[rchrd2]

An example in the README on how to use and configure this would be very helpful.

[TannerW]

Any updates on this?

[bionicles]

I'd use it! just some basic usage example would be clutch

[dmonad]

Hi @bionicles , thanks for your interest! Just a heads up: Unfortunately, I currently don't have time to work on it. If you are willing to, I'd be happy to help you out if you contribute to this repository.

[bionicles]

sure, I love me some Redis, and CRDTs are fascinating.

Question:

  const redis = new Redis()
  await redis.flushall()
  {
    const redisPersistence = new RedisPersistence()

how does RedisPersistence find out about Redis?

[dmonad]

You set the address as a parameter of the RedisPersistence (the default is localhost)

[chanced]

@dmonad it may make more sense to either accept a factory for redis/cluster clients or 2 instances rather than the configs.

I think its a bit more clear and helps with testing / separation of concerns.

[ahoyahoy]

+1
please!

[datzun]

+1

[appletea233]

plz +1

[petru-planable]

+1