Mokacchi
CDCloudflare Developers
•Created by Mokacchi on 4/14/2025 in #general-help
Is there a way to protect workers with a Cloudflare Login? (Access)
Hi, I'm still a beginner on the cloudflare platform, and so far I figured out that I can use Zero Trust -> Access to protect my worker from public access, for example for preview deployments. But without using an external oauth provider, I only managed to protect them via "email access code", where I also have to manually manage the email whitelist in the rule itself.
Is there a way to protect a worker using a Cloudflare login, so that team members of the project can access it but others cant?
1 replies
CDCloudflare Developers
•Created by Mokacchi on 4/12/2025 in #workers-help
"Update name in Wrangler configuration file to match deployed Worker" even though name is the same
Hey everyone,
I took an existing github project of a cloudflare worker, removed my old deployed workers via the dashboard and then created a new one from that github repo. Reason being that I'm switching from my self-built github actions to the new worker preview feature.
So I enabled it and now every time I push, the cloudflare integration opens a pull request to change the name of the worker in the worker configuration. The issue is that the name is exactly the same, and said pull request ends up with no file changes.
My worker is built using react-router and the cloudflare vite plugin.
I defined a "production" environment in the wrangler configuration,
Which means I'm setting the environment to use at build time, not at deploy time.
Since the vite plugin creates its own internal wrangler config, is this what causes the bug? Since deploying on the production env will change the name to "<worker_name>-production"?
The documentation says that the environment names shouldn't cause this issue.
However my original connection to github initially deployed the "default" environment, so the suffix is not there..
4 replies