Mokay thanks that makes sense actually
Mand also i wanna say i was using wrangler before v3 and now this is way better dx with the local dev mode great work guys 
Cminor but you can return your own cf-cache-status header from a worker, probably not a good idea, but I mean if you wanted to, could fake a miss
EFun, okay then
UYeah workers can add cf-<anything> just the rules stuff cant. or at the very least a few of the cf-<things> I tried worked
Ccan't override cf-ray but lots of other things you can fake
Mthis cache api is actually nice you can upload stuff and instantly insert in your cache aswell so even the first request can be cached, very cool
ODoes anyone have recommendations for a rate limiting library backed by D1 or KV?
UKV shouldnt really be used for rate limiting as theres a limit to writes on the same key to 1 per second. Not aware of any rate limiting libraries with D1 though, only rate limiter I am really aware of is this repo with the code for making one with durable objects: https://github.com/honzabit/durable-limiter
UOf course would highly recommend using cloudflare waf rate limiting rules if you can (they are free and unmetered now they used to be paid)
QQuick question around durable objects and setAlarm. Since Date.now() will only return the time of the last IO, the below example may set the alarm to a past time. Is this correct? Is the alarm still guaranteed to execute in that case?
DYour observation is correct, fortunately the documentation says that setting an alarm for a past date triggers immediately
DAha, found the docs: https://developers.cloudflare.com/durable-objects/api/transactional-storage-api/
If setAlarm() is called with a time equal to or before Date.now(), the alarm will be scheduled for asynchronous execution in the immediate future. If the alarm handler is currently executing in this case, it will not be canceled. Alarms can be set to millisecond granularity and will usually execute within a few milliseconds after the set time, but can be delayed by up to a minute due to maintenance or failures while failover takes place.
The Transactional Storage API allows you to achieve consistent key-value storage.
ESo is it still safe (from spoofing) to use MailChannels pages plugin so long as you have SPF, DKIM, and DMARC setup properly?
Qthank you so much for pointing this out, didn't see this part! Great to know
EHow do I pass a template to the mailchannels pages plugin? Is that possible? I see that it has a
content property, but I don't understand why it's an array.
CNever used it but what does your code look like?
HUsing Image Resizing with Workers gives you powerful programmatic control over every image request.
HTheoretically, yes
HWait
HMaybe
HI think this is a try it and see moment
CIt would be very janky and not officially supported so probably isn’t worth the trouble.
KI'm pretty sure putting a Worker on top of pages.dev bricks it until you do another Pages deployment
KYou can use Functions - they're Workers but integrated with Pages
KSame pricing
SI'm not sure where to ask this so let me know if I should delete this and move to another channel.
Has anyone set up a GitOps CI/CD for Workers similar to what Pages (and Vercel etc) have for FE projects? E.g., each branch is deployed independently (configured with preview secrets etc)?
Has anyone set up a GitOps CI/CD for Workers similar to what Pages (and Vercel etc) have for FE projects? E.g., each branch is deployed independently (configured with preview secrets etc)?
ASo I am a little confused, whats the limit on Pages & Workers projects? Is there one? If it hit it can I get it increased? Whats the rules here?
Dis there any way to host a jar file on cf workers? Maybe a docker container?
Chttps://developers.cloudflare.com/workers/platform/limits/
On Workers Free, you can have 100 Workers. On Workers Paid, 500.
https://developers.cloudflare.com/pages/platform/limits/
For Pages Projects
On Workers Free, you can have 100 Workers. On Workers Paid, 500.
https://developers.cloudflare.com/pages/platform/limits/
For Pages Projects
Projects
Cloudflare Pages has a soft limit of 100 projects within your account in order to prevent abuse. If you need this limit raised, contact your Cloudflare account team or use the Limit Increase Request Form at the top of this page.
In order to protect against abuse of the service, Cloudflare may temporarily disable your ability to create new Pages projects, if you are deploying a large number of applications in a short amount of time. Contact support if you need this limit increased.
Aok good to know, i was looking at the workers landing page and it said up to 100 for free but didnt say 500 for paid, wasnt sure.
just wanted to make sure since i throw every random project idea i have onto cf pages and/or workers
just wanted to make sure since i throw every random project idea i have onto cf pages and/or workers
CWorkers run as V8 Isolates, same Javascript Engine as chrome, similiar environment. Can't run Docker Containers. Javascript is the main language, otherwise other languages can be used in Workers via WASM and Bindings back to Javascript, but there's a 10 MB Worker Size Limit that heavily limits what you can do. You'd have to fit the entire runtime and code within that. Additionally Workers can only be triggered on incoming http requests (no tcp/udp unbound) and can only make tcp outbound via a special mechanism, and they don't last for long, need to have fast startup time (400ms max)
Dokay thank you, i can compile to JS as it’s made in kotlin, not too sure how well it’s going to run though
Dah 400ms might be the end of my dream
