feat(socket): prepare Redis multi-instance support (#45) #70

Merged

Reliodas merged 1 commit from feat/45-multi-instance into develop

2026-06-26 00:31:47 +00:00

Reliodas commented

2026-06-26 00:23:05 +00:00

Owner

Closes #45

Summary

add optional Socket.IO Redis adapter wiring through REDIS_URL
add lazy Redis hydration for room:resume across instances
add client room query updates so reverse proxies can keep room affinity
document the deployment choice and provide a two-instance Docker Compose scenario

Verification

npm run typecheck
npm test
npm run test:coverage
npm run build
npm run validate:questions
npm run check:assets
npm run smoke
npm run test:e2e
docker compose -f docker-compose.multi.yml config

Notes

Redis adapter integration coverage is skipped unless REDIS_URL points to a real Redis instance.
Active gameplay authority remains local to an instance, so production multi-instance deployment requires room affinity until a fully distributed game engine is implemented.

Closes #45 ## Summary - add optional Socket.IO Redis adapter wiring through REDIS_URL - add lazy Redis hydration for room:resume across instances - add client room query updates so reverse proxies can keep room affinity - document the deployment choice and provide a two-instance Docker Compose scenario ## Verification - npm run typecheck - npm test - npm run test:coverage - npm run build - npm run validate:questions - npm run check:assets - npm run smoke - npm run test:e2e - docker compose -f docker-compose.multi.yml config ## Notes - Redis adapter integration coverage is skipped unless REDIS_URL points to a real Redis instance. - Active gameplay authority remains local to an instance, so production multi-instance deployment requires room affinity until a fully distributed game engine is implemented.

Reliodas added 1 commit

2026-06-26 00:23:06 +00:00