Repository navigation
docs(examples): run the Cloudflare example on D1 and a Durable Object - #324
Merged
Merged
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.
F-03 task 14, the example half. The full Cloudflare Worker example now uses
@chatcops/store-cloudflare:ChatCopsCounterDurable Object (exported from the Worker).ctxto the handler, so webhooks and analytics writes finish after the reply.retention, a realallowedOriginsand aglobalPerDaybudget.wrangler.tomlgets the D1 binding, the DO binding with its SQLite migration, andnodejs_compat. The page also haswrangler d1 create, a note on running without the DO (counters in D1), and a link to the scheduled purge recipe.The small example in
packages/server/src/examples/cloudflare-worker.tsswaps the deprecatedcorsforallowedOrigins. An empty changeset covers that, since it is only an example.The store package is not on npm yet: it is at 0.1.0 and still private until its first publish. This page only goes live with the next release, which should come after that publish.
Checks: the website builds, and so does the server.