~~KV listing in the dashboard seems to be broken?~~ ~~namespaceId: `1febbc2176164bb28d7cd90ab661e86
1febbc2176164bb28d7cd90ab661e862edit: the only fix was recreating the namespace
O
Chey everyone, I have a nextjs app that is a worker. I also have a binding for KV ready. How can I use it directly with binding in the app? KV store in NextJs App I decribed it in more details here
ZI don't think it's possible to do that. If your worker only does KV reads/writes, perhaps turning off the routes there could be a solution?
ZIf your worker does more, I don't really have a good solution for you :/
1Put auth on the Worker so a bad actor can't access it?
1Per user rate limiting of some kind then perhaps
1What do you mean? You said you wanted to avoid KV reads
Something like this depending on how much effort you want to go to: https://developers.cloudflare.com/durable-objects/examples/build-a-rate-limiter/
Something like this depending on how much effort you want to go to: https://developers.cloudflare.com/durable-objects/examples/build-a-rate-limiter/
1Then you'd need to implement something client-side, which doesn't render my suggestion useless, just wouldn't be using Workers to do so
1:bye:
BICMP doesn't invoke your worker if that's what you're implying
BI figured as much, was a just-in-case
1How is your site hosted, on CF with Workers/Pages? What is the KV storing, and how is the client-side accessing it?
1Sounds like you need to host the site on Static Assets which would be free unlimited requests if you are serving static HTML files
1Could you store in D1 for way more reads?
1What is the data on the pages?
1Like I said, if you aren't invoking a worker at all then Static Assets are free and unlimited
1Yeah that wil help for sure
1And what is being built exactly? We can help better if we actually understand what it is you're doing
1Right now its super vague as a website could be anything
BMight want to give the firewall blocking a try too
1Good call, there's a bunch of stuff that CF has that can help fight malicious and bot traffic
1Can we look at the site? That description is about as vague as you could possible be
BIt doesn't really matter, he can't use static assets because the site isn't static
BIt's not a bad suggestion from @1984 Ford Laser if you're willing to go the route of SSG - you'd never have to worry about a request bill
1Blog seems like a perfect use case for Static Assets, especially if it isn't a big site. If you aren't adding pages regularly, in theory, you could load your current pages via Workers/KV, save them as HTML, then serve those pages using Static Assets. I'm simlifying a bit, but there are ways forward here
B500 builds per month on the free tier, if you're up for the task of rewriting
1So in theory you could just save the pages in your browser, then upload those assets as static assets
BDoubt it's worth it to you to rewrite the thing then. Slap on some firewall rules and turnstile
T@OSC you should be able to use rate limiting and user a user id (or even their cf-ip) as the rate limiting key https://developers.cloudflare.com/workers/runtime-apis/bindings/rate-limit/#:~:text=The%20key%20you%20provide%20can%20be%20any%20string%20value.
Cloudflare Docs
Define rate limits and interact with them directly from your Cloudflare Worker
BThis still invokes the worker, he's trying to avoid the request charges
