- collector
- agent report
- workers cron (queues)
- records pagination
- chart
- user manager
- export/import
-
limits
-
cloudflare & websocket
- https://blog.cloudflare.com/introducing-websockets-in-workers/
Our current thinking is that when using WebSockets, you'll be charged for wall clock time whenever a message is being processed by the Durable Object on any WebSocket connection - this charge would be shared across all WebSockets connected to a given Durable Object. When there is no CPU activity on a Durable Object, but any number of WebSocket connections remain established, you'll be billed a much lower active connection charge, per second.
- https://github.com/AggressivelyMeows/cfw-easy-utils/blob/970990b3f24d60343c3d92b2f6dd5ebd5cb8c2a6/src/websockets.js
- https://blog.cloudflare.com/introducing-websockets-in-workers/
-
pages & functions & impl
-
kv
- https://uptimesniper.com/blog
- https://developers.cloudflare.com/kv/learning/how-kv-works/#consistency
Changes may take up to 60 seconds or more to be visible in other global network locations as their cached versions of the data time out
-
auth & iam & oidc
- https://github.com/subhendukundu/worker-auth-providers
- https://github.com/subhendukundu/worker-auth-providers/tree/main/example/functions/api/v1/auth/github
- https://mecanik.dev/en/posts/cloudflare-pages-register-login-and-user-system/
- https://developers.cloudflare.com/pages/platform/functions/plugins/cloudflare-access/
- https://github.com/search?q=cloudflare+workers+oauth&type=repositories
- https://github.com/search?q=cloudflare+workers+auth&type=repositories
- https://github.com/eidam/cf-access-workers-oidc
-
protocols
-
others
- https://docs.astro.build/en/guides/deploy/cloudflare/ | github
- https://nitro.unjs.io/deploy/providers/cloudflare
- https://github.com/honojs/examples/tree/cc93499076475b7138b499343b38ad6f34e52b00/pages-stack
- https://github.com/microfeed/microfeed
- https://blog.cloudflare.com/zh-cn/production-saas-intro-zh-cn/