Anyone have an idea why console.log would be forwarded through worker logpush but using a library like loglevel wouldn't (which uses console.log under the hood)

does a JSON schema from

wrangler.json

exists somewhere? https://developers.cloudflare.com/workers/wrangler/configuration/

Not currently

But it's something that was being talked about

I'd recommend you make an issue, asking for support!

Is it ever common to call a worker from another worker that's a cron trigger?

I'm thinking of creating a worker with a cron trigger, that's simply responsible for calling the worker function from a schedule. the worker function i'm calling on a schedule will be using Hono, and will have more complex operations. I was thinking it might be nice to separate the concerns, and have one cron trigger worker just designated to calling the worker

Not sure why you wouldnt just run the code directly in the cron but you can use service bindings

Depending on what you need in your

fetch

handler I'd just do

ctx.waitUntil(this.fetch())

in your

scheduled

handler

dope thanks to both answers ^

is it possible, to have an email worker recive an email, then to have that email displayed on a cloudflare page? I haven't worked with workers before and im not sure how or if diffent parts of them can interact like that?

awesome

On a page behind Cloudflare? Sure! You can use the email worker to store it to something like KV, R2 or D1, then fetch it from there again to display it on a webpage. If you mean displaying it on the CF dashboard, then no, that's not currently implemented and I'm not aware of any plans for that.

yes to a webpage, where i am struggling is how to get the email worker to upload to the R2 bucket

Where in that are you stuck?

okay so first how to get the content of the email, i think its like this

message.headers.get('subject')

or

message.headers.get('body')

now im just lost at how to upload that to R2

okay so in this

export default {
  async fetch(request, env) {
    const url = new URL(request.url);
    const key = url.pathname.slice(1);

    switch (request.method) {
      case 'PUT':
        await env.MY_BUCKET.put(key, request.body);
        return new Response(`Put ${key} successfully!`);

i don't under stand this line

const key = url.pathname.slice(1);

thats from r2 docs.

URL.pathname is a string, such as

/my-path-here

. You don't want to include that initial slash, so you use

.slice(1)

to make it just

my-path-here

🙂

ahh okay so "key" is the path of the upload?

how do i authenticate to put into the bucket?

Correct

What do you mean by this - authenticating users? If so, there are lots of ways to do this, you could check the headers in your worker, you could use firewall rules, cloudflare access, etc. If you mean your worker authenticating to R2, there's no need for that, it's handled automatically

yes ment the worker, figured since no docs mentioned auth it was just handled.

Yep, it's all done through cloudflare magic 😅

yea lot of magic I am far from understanding lol

So is everyone when they first start! We're here to help you work out the problems you encounter, feel free to ask whenever you need it

okay can you tell me where i am going wrong?

export default {
  async email(message, env, ctx) {
    const key = message.headers.get('subject')
    const msg_body = message.headers.get('body')

    await NAME_OF_MY_BUCKET.put(key, msg_body)

  }
}