-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Update Storage in Lambda Environment #1274
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm building a multiplayer real-time CRM that requires inserting values into the JSON storage object from outside of the room context. For example, someone submits a support ticket on a page that is outside of a room context. Currently, this is a multi-step process.
POST /api/ticket
). <-- This is a Vercel serverless functionCurrently, my understanding is that websocket connections are required to modify storage which is not supported in a Vercel Lambda. Furthermore, these updates don't work if the room is at capacity. While I don't foresee this being a major issue, it is still an edge case. Ideally, I would like to replace steps 3 and 4 with an API call to liveblocks.
Describe the solution you'd like
To be clear, I'd like to be able to just make a simple API call to modify liveblocks storage that is compatible with a serverless environment. Ideally, it would be something similar to this: https://liveblocks.io/docs/guides/modifying-yjs-document-data-with-the-rest-api.
Additional context
The other documentation for modifying the storage objects will cause all users to be disconnected from the room. I think this is okay as, I could simply have users automatically reconnect once the write is finished.
The text was updated successfully, but these errors were encountered: