Add submission: Socket.IO Valkey Adapter — Stalwart Team#8
Add submission: Socket.IO Valkey Adapter — Stalwart Team#8webdevelopersrinu wants to merge 5 commits into
Conversation
Add submissions/socket-io-valkey-adapter_stalwart-team.md for Problem statement 1 — Track A Integration reacthyderabad#27 (Socket.IO native Valkey adapter).
|
Thank you for the great work on getting this project started; can you please make me @rlunar maintainer? so I can make a request to adopt this repo under the official @valkey-io org. |
|
Hi @rlunar — thank you so much, this means a lot to our team! We'd be honored to have socket.io-valkey-adapter adopted under @valkey-io. Yes, happy to add you as a maintainer on the repo so you can start the adoption request. Could you let us know the best next step — should we add you as a collaborator on https://github.com/webdevelopersrinu/socket.io-valkey-adapter, or transfer the repo to the org directly? Whatever process @valkey-io prefers works for us. One small request: we'd love for our team (Stalwart Team — Sai Krishna Jamanjyothi, Aditya Sathwik Dasari, Chandra Sekhar Kalisetti, and Srinu Desetti) to remain credited as the original authors/maintainers(if possible). Beyond that, we're fully on board and excited to keep contributing — including the streams-based variant and Valkey Cluster support on our roadmap. Thanks again for the opportunity! 🚀 |
2 participants
Submission: Socket.IO Valkey Adapter
Adds the project submission for Stalwart Team under
submissions/.File:
submissions/socket-io-valkey-adapter_stalwart-team.mdProject
A native Valkey adapter for Socket.IO — the equivalent of
socket.io-redis-adapter, rebuilt assocket.io-valkey-adapterto enable real-time, multi-server WebSocket broadcasting powered by Valkey. Published to npm and live.Problem Statement
Problem statement 1 — Track A Integration #27: Socket.IO — add a native Valkey adapter.
Links
Team — Stalwart Team
Checklist
submissions/folderprojectname_attendeeName.mdfollowed