Access on Workers docs #25603
Access on Workers docs #25603
Conversation
GregBrimble
requested review from
a team,
WalshyDev,
irvinebroque,
kodster28,
korinne and
mikenomitch
as code owners
github-actions
bot
added
size/m
October 2025
product:workers
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
GregBrimble
force-pushed
the
access-docs
branch
from
39452b7 to
6b94fa0
Compare
irvinebroque
left a comment
irvinebroque
left a comment
There was a problem hiding this comment.
We previously had this image in the blog which was really nice
Should we use it here? You take one look at this and you get it pretty instantly, and it's well presented
| try { | ||
| // Create JWKS from your team domain | ||
| const JWKS = createRemoteJWKSet( | ||
| new URL(`${env.TEAM_DOMAIN}/cdn-cgi/access/certs`), |
There was a problem hiding this comment.
I like including the code snippet in the changelog, and the guidance
If we are going to do that we might need to guide people though on (1) where these env vars come from and (2) how to set them
There was a problem hiding this comment.
Or alternatively — just link there?
There was a problem hiding this comment.
ah, sorry, missed those from my copy-paste of your code snippet. Adding now! (I think good to copy rather than just link so it's all in one place and pads the changelog out a bit).
|
|
||
| All Workers are assigned a `workers.dev` route when they are created or renamed following the syntax `<YOUR_WORKER_NAME>.<YOUR_SUBDOMAIN>.workers.dev`. The [`name`](/workers/wrangler/configuration/#inheritable-keys) field in your Worker configuration is used as the subdomain for the deployed Worker. | ||
|
|
||
| ## Manage access to `workers.dev` |
There was a problem hiding this comment.
Nice one adding this here
GregBrimble
force-pushed
the
access-docs
branch
from
829c790 to
e9b64f3
Compare
11 participants
Summary
Changelog and docs for Access in front of Workers
Documentation checklist