docs(cloudflare): add DO worker setup for skew protection#211
Open
alex-all3dp wants to merge 1 commit intoopennextjs:mainfrom
Open
docs(cloudflare): add DO worker setup for skew protection#211alex-all3dp wants to merge 1 commit intoopennextjs:mainfrom
alex-all3dp wants to merge 1 commit intoopennextjs:mainfrom
Conversation
This file contains hidden or 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
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.
@vicb I added a new section to the skew protection page explaining how to use Durable Object-based overrides (
doShardedTagCache,doQueue,purgeCache) together with skew protection.The existing skew protection docs state that DOs need to be in a separate worker, but don't explain the setup in detail. This added section covers:
script_namebindings in the main worker,WORKER_SELF_REFERENCEin the DO worker)I hope this aligns with the multi-worker setup you were referencing in your initial answer. Happy to adjust it further of course or learn about possible shortcomings in the path we chose.
Closes opennextjs/opennextjs-cloudflare#834