cloudflare-docs VS flow-pipeline

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

Many Thanks to Cloudflare and dev.to for giving us this opportunity.

Unlike other providers in this list, Cloudflare is not just a serverless database platform. Instead, it’s a cloud connectivity platform that provides several web services. It’s one of the world's largest networks and serves 55 million HTTP requests per second.

Using a Content Delivery Networks (CDNs) such as Cloudflare, can help absorb large amounts of traffic and mitigate the impact of DoS attacks.

When a user requests a webpage, the CDN delivers the content from the nearest server to the user. As a result, the loading times are faster since the data has to travel a shorter distance. CDNs offer endless benefits like reduced bandwidth usage, scalability, increased reliability, and more. Some well-known CDNs include Cloudflare, Amazon CloudFront, Akamai, and Fastly. They offer several features that help reduce web page sizes and make websites run better.

Cloudflare

Cloudflare offers low/no markup domain name registration with a free DNS service. This will virtually always be your cheapest option for domain name renewals. They don't list prices for all TLDs upfront, so use this list to get your best estimate.

Our site used Cloudflare to handle all our DNS needs. Cloudfare has a number of rewrite options but as we needed to make a decision based on a) the URL path and b) rewriting to a specific domain, the only option (as a non enterprise customer) was to use Cloudflare workers (via worker routes).

Add Cloudflare Cahce & Protection

Cloudflare is a cloud-provider, most-known for their CDN, offering several services to build cloud applications. Among them, Cloudflare Workers is a serverless service that allows you to run serverless functions at edge (like Lambda@Edge if you are an AWS user). This means that your code runs closer to end-users, resulting in blazing fast response times.