feat: Configure In-Memory or Redis-backed GraphQL Live Query and Subscriptions #8791
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dthyresson
commented
Jun 30, 2023
packages/cli/src/commands/experimental/templates/realtime.ts.template
Outdated
Show resolved
Hide resolved
dthyresson
commented
Jun 30, 2023
dthyresson
commented
Jun 30, 2023
dthyresson
commented
Jun 30, 2023
|
I also have to completely redo docs and community post now as lots of setup has been simplified. |
dthyresson
commented
Jun 30, 2023
dthyresson
changed the title
|
I need to remove that es lint and just realized I should add a few more uaeRedwoodRealtime tests for the pubSub and new config |
|
I had a new idea. May I use the real-time to define the config and import that in the server. In long run that may be easier to manage and codemod updates. |
I have moved redwood Realtime config into the lib and import that now in server file so it is cleaner. Tests added to confirm that the store is created for LQ and pubSub for Subs. |
packages/cli/src/commands/experimental/templates/realtime.ts.template
Outdated
Show resolved
Hide resolved
jtoar
pushed a commit
that referenced
this pull request
Jul 4, 2023
…criptions (#8791) This PR refactors the Live Query and Subscription configuration for Redwood Realtime to move more boilerplate setup to manage the stores and behavior into the framework rather than in the app. Redis or in-memory stores can be setup. One might use in memory for dev, and then Redis for prod, etc. See: https://the-guild.dev/graphql/yoga-server/docs/features/subscriptions#distributed-pubsub-for-production Redis and IORedis clients have been tested; Upstash Redis doesn't seem to work as it can publish but not subscribe? Have to confirm.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR refactors the Live Query and Subscription configuration for Redwood Realtime to move more boilerplate setup to manage the stores and behavior into the framework rather than in the app.
Redis or in-memory stores can be setup. One might use in memory for dev, and then Redis for prod, etc.
See: https://the-guild.dev/graphql/yoga-server/docs/features/subscriptions#distributed-pubsub-for-production
Redis and IORedis clients have been tested; Upstash Redis doesn't seem to work as it can publish but not subscribe? Have to confirm.