example@mydomain.com and example+foo@mydomain.com to send email to that worker?
example@mydomain.comexample+foo@mydomain.com
A
S
P
export default {
async fetch(request) {
const url = new URL(request.url);
url.hostname = 'my-custom-pages-site.pages.dev';
return fetch(url.toString(), request);
}
};
Bnot_found_handling so it only routes to my worker if the path matches /api"/api/*"?B
A
CAB
D
SS
op run -- wrangler dev and it will pickup the local secrets from environment variables that have 1Password Refs in them (op://Private/Vault/GitHub/token)SSwrangler dev --remote .. the binding is a SecretsStoreSecret and it gets the value from the real secret store. I'm confused how this works. Should this work? Doesn't this basically give everyone on the team access to the secrets? Just console.log() them in your local env?S
SS
CC
S
MSS
When to keep multiple endpoints in a single worker: When to split into separate workers:
P
IS
IS
IIISS
S
A
ZSIISI
fetch handler (which Hono handles for you, in that example) is "global"SSAAA given isolate has its own scope, but isolates are not necessarily long-lived. An isolate may be spun down and evicted for a number of reasons
Because of this, it is generally advised that you not store mutable state in your global scope unless you have accounted for this contingen
A
SSexport default {
async fetch(request) {
const url = new URL(request.url);
url.hostname = 'my-custom-pages-site.pages.dev';
return fetch(url.toString(), request);
}
};not_found_handling"/api/*"op run -- wrangler devop://Private/Vault/GitHub/tokenwrangler dev --remoteSecretsStoreSecretconsole.log()fetchconst app = new Hono()
export default app;
CDCloudflare Developers / general-helpCDCloudflare Developers / workers-and-pages-helpCDCloudflare Developers / workers-and-pages-helpCDCloudflare Developers / general-help