Or in the dashboard you can just toggle it

Thanks a lot!

Hello. I am deploying to Cloudflare Pages via a Github action. Once it has finished, the last part of the output is

:sparkles: Deployment complete! Take a peek over at https://randomnumber.mydomain.pages.dev

Is it possible to get that url set as an environment variable so I can use it in a further step. Appreciate this may be more of a Github Action question but also wondered if there was a CLI option when using the command

pages publish public

? Thanks

If you use pages-action () it will provide the

url

as an output of the action, see the "Outputs" section at the bottom of the readme

will setting

cacheLevel

to

bypass

work ?

Sample code:
await fetch(request, {
    cf: {
      cacheKey,
      cacheLevel: 'bypass'
    },
  });

No, because any modifications you make with the Fetch Cache API are only applied on subsequent requests. The regular Cache API supports modifications on the first request, which is why I recommended it

oooh thanks. I am currently using https://github.com/cloudflare/wrangler-action I'll try your suggestion

Hi all, my worker exceed CPU startup time. How do I increase it? I have test with AWS Lamda, startup time is about 2000ms. Other event is below 5ms

But aws lamda is unicast and not friendly to debug :))) so I prefer Cloudflare worker

You can’t increase startup time. At the moment, what we recommend instead is to look at what you are doing at startup, and remove it where possible, or delay it if not

Thank you for your answer. Everything I have done is import ethers.js module and initialize its provider, when I remove it, everything works correctly

Yeah, I’ve noticed that crypto-related packages are generally pretty bad when it comes to starting up fast.

Thank you, so sad to hear it so I think this problem can not solve, isn't it?

Unless you want to write your own crypto library, then probably not...

Thank you so much

No problem!

How can I verify in my fetch handler that it's only being called by a fellow Worker in the same account through a service binding?

You could add something to the

cf

object in the Request?

Will

cf.worker.upstream_zone

be present for a service binding?

That's apart of the ruleset engine only - rather than the

cf

object on a request

oh

Is the Worker you're calling ever called by anything other than the service binding?

it shouldn't be; I'm trying to prevent a situation where somebody accidentally hits a button in the dashboard and publishes the Worker on a public route lol

I was gonna say haha, just add no routes & disable workers.dev and you're basically done

What HAW was saying is that if you do

await env.FOO.fetch(url, { cf: { lol: true }});

then

req.cf.lol

should be present on the

FOO

Worker

one way to find out

yeah that's right

same as with wfp