cloudflare-docs VS miniflare

Slightly related - CloudFlare account_id and zone_id are safe to be public

https://github.com/cloudflare/cloudflare-docs/issues/474

https://community.cloudflare.com/t/api-zone-id/355566

> The Zone ID and Account ID are not sensitive. Sensitive data like account API Key, Secrets etc. can all be revoked, rotated or changed. See the comment 36 below on the Wrangler repo: as per our security team, it’s completely Fine to have your zone_id and account_id public, the Global API key and associated email address should be kept secret.

I have created an issue in their docs repository to address that misleading statement.

I don't strictly know if this is related, but the terms are being revised due to the release of R2: https://github.com/cloudflare/cloudflare-docs/issues/7186

CloudFlare cannot protect applications that use # in URLS: https://github.com/cloudflare/cloudflare-docs/issues/7062

https://www.youtube.com/watch?v=KMEgJRqYzzg https://www.youtube.com/watch?v=QcXmGQqtUn0 https://www.youtube.com/watch?v=5dkzFrJ044o https://www.youtube.com/watch?v=48NWaLkDcME https://www.youtube.com/watch?v=4lGzIZqVN8Q https://www.smashingmagazine.com/ https://www.cloudflare.com/ https://prerender.io/ https://developers.cloudflare.com/

You can check the changes here: https://github.com/cloudflare/cloudflare-docs/commits/produc...

We're working on the documentation, I agree it can certainly be thin (or just not understandable). Please do file an issue for any improvements you'd like to see: https://github.com/cloudflare/cloudflare-docs/issues

I think you can also implement it as a private route via the gateway, so you access the private address of bitwarden instead of bypassing auth to a public host name (this I haven’t tried, but maybe another worthwhile option?) https://github.com/cloudflare/cloudflare-docs/blob/production/content/cloudflare-one/tutorials/zero-trust-network-access.md

Recently Cloudflare introduces Miniflare. As its name suggests, Miniflare is a feature-rich but miniature version of Cloudflare worker. Miniflare is a simulator that provides an environment for developing and testing Cloudflare worker scripts locally. Miniflare is written in typescript and supports most of the Cloudflare worker features like the KV database, durable objects, WebSockets, etc.

Another implementation of the above is Cloudfare workers you might be capable of grasp some ideas from here https://miniflare.dev

Is there an ETA on Miniflare v3? Ran into a problem recently using overlapping keys with forward slashes as they were not sanitized properly: https://github.com/cloudflare/miniflare/issues/167

The KV API is only available on Cloudflare Workers. But, during development, Rakkas runs our app on Node.js. Fortunately, the Miniflare project has a KV implementation for Node. The other two packages that we've installed (@miniflare/kv and @miniflare/storage-memory) are what we need to be able to use the KV API during development. Let's create a src/kv-mock.ts file and create a local KV store to store our ublog posts ("twits") while testing:

I used hono (a wrapper around miniflare) to handle some of the boilerplate around request and routing logic. It's also refreshingly fast! 🔥

The simple explanation is that I'm proposing use of the Service Worker API. Cloudflare offers a flat, free, 100k requests a day if you can keep it cutting edge, has local development and testing options with miniflare and a key/value (KV) store.

When we run the dev script, this will ensure that the local runtime environment Miniflare will bind a KV with the name sessionStorage to our Pages function.

Slshx is a library for building strongly-typed Discord commands (https://discord.com/developers/docs/interactions/application...) that run on Cloudflare Workers (https://workers.cloudflare.com/), using a React-inspired syntax (hooks and JSX). It supports all Discord command types/options, autocomplete and interactive message components. During development, it automatically deploys your commands whenever you change your code.

I created this because I think Cloudflare Workers are a great fit for hosting Discord commands, but there wasn't an easy way to get started that had a fun development experience. I also wanted to see what a Miniflare-first (https://github.com/cloudflare/miniflare) library could look like.