No, but you can put the account ID in your `wrangler` config
No, but you can put the account ID in your
wrangler
Awe probably shouldn’t be generating too many… 10K simultaneous sounds like a bug of some kind for sure. we probably only spin up several hundred DOs in a 10 minute period
Jthat's not ideal as it's my work account and I don't want it to affect my personal account
Jso I really want it to be global but just for the project/directory/monorepo
HNot sure I understand? If you put the ID in your config, then it only applies to that one Worker/Pages Project
Joh, I think I misunderstood what you meant by "your" config.. do you just mean the project config? there are many workers in my monorepo, wanted to avoid hardcoding the account id into all of them
HYeah, that's what I meant. There isn't currently a way to make them inherit an account ID from somewhere else
HUnless you want to add an Environment Variable that you can somehow scope to just that directory
Johh, that could work
Lwhy is pages recommend over worker sites? It seems like Worker Sites is more powerful
CIn what way? Pages has built in CI/CD, supports advanced mode so you can pop out of the provided stuff and use it more like Worker Sites, free unlimited static asset requests, versioning/rollbacks/etc
Lcan't seem to use durable objects / D1 Transactions but maybe I'm doing something wrong?
DYeah, the functionality venn diagram of Workers/Workers Sites and Pages/Pages Functions is... a bit awkward imho.
CDurable Objects have to be defined in a worker and then you can attach to in Pages, Explicit Transactions don't exist outside of batch
CThey're working on converging Pages and Workers into one product: https://blog.cloudflare.com/pages-and-workers-are-converging-into-one-experience/
The Cloudflare Blog
Today we’re excited to announce that over the next year we will be working to bring together the best traits and attributes you know and love from each product into one powerful platform!
DYeah, I'm very much looking forwards to that!
Cit's a little awkward right now, Pages still has a ton more stuff then normal Workers, would hardly say Worker Sites is more powerful outside of a few edge-case not supported stuff/bindings
L@Chaika I thought you could provide a transactions.js file? https://blog.cloudflare.com/whats-new-with-d1/
The Cloudflare Blog
Get an inside look on the D1 experience today, what the team is currently working on and what’s coming up!
C"Sneak peek"
DFor now I'm mostly doing my FE in Pages and my services as Workers, and just using lerna monorepo (sometimes combined with git submodules) to manage the whole thing.
L@Chaika hmm, so if I wanted to build a social network on cloudflare, would that be something that would not make sense to do given the current scope of features that exist?
CIt has implicit transactions with batch/queries
CCloudflare Docs
D1 is compatible with most SQLite’s SQL convention since it leverages SQLite’s query engine. D1 client API allows you to interact with a D1 database from within a Worker.
LDecision fatigue is getting the best of me with all of this new tooling 
CIt depends exactly how you want to build it how you'd go about it, but I don't see any reason why it would be impossible, D1 is semi-limited though because right now it's a single javascript thread/isolate in a single location, so for dynamic social networks which aren't too cachable you might reach the limits of one + the max size of 10gb per db
Cthey want you to scale with more DBs but doing that with a social network would be interesting, I guess could have each user in its own D1 DB but would need a lot of glue + the tooling to handle that all well/dynamically is still unreleased
LSQLite Cloud offers an easy way to share single-user SQLite databases to the cloud. We offer enterprise features like advanced scaling solutions, continuous backup, ACID-compliant over multiple nodes (and multiple zones), pub/sub capabilities, powerful users/roles access control, and a javascript-based programming language to extend the built-in...
Cyou mean instead of d1? That's basically what D1 aims to provide eventually in some ways, although I would note their storage limits are no better/probably same other arch limits to a degree if that's why you don't want to use d1
CThe advice of the D1 team has been if you want a monolithic db/one big db you should go with another provider and use an http api or #hyperdrive
Lyeah, I honestly don't know what I'm doing, I'm an expert in front-end but, building full fledged services is not something I've done actively
L@Chaika does Hyperdrive work in pages?
LLGitHub
GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.
JI have a CF worker (worker A) that exposes different endpoints using Hono, now I have another worker (Worker B) that needs to make a request to Worker A. Is it possible to make an RPC service binding call to a Worker A method, if so how would I achieve this, any documentation or examples appreciated.
JHey All,
Is it possible to use worker from ourside of the cloudflare zone?
Like CNAME the worker sub-domain from Go-Daddy?
Is it possible to use worker from ourside of the cloudflare zone?
Like CNAME the worker sub-domain from Go-Daddy?
JThanks @FlikTeoh, totally agree the docs are impressive, I have read the RPC documentation and implemented it across other workers, this scenario is slightly different from documented. Or at least I couldn't work out from the docs how to implement my scenario...
I have a worker with the following simplified code:
In order to do a service to service binding I have the RPC or fetch option. With the RPC approach I have to export a class that extends
If I want to use the HTTP fetch interface how would I export a fetch handler and also the other endpoints via Hono?
I'm starting to wonder if there is a problem with my solution design, might rethink it, in the meantime any examples or pointers appreciated.
I have a worker with the following simplified code:
In order to do a service to service binding I have the RPC or fetch option. With the RPC approach I have to export a class that extends
WorkerEntrypoint , in which case how do I also export the endpoints?If I want to use the HTTP fetch interface how would I export a fetch handler and also the other endpoints via Hono?
I'm starting to wonder if there is a problem with my solution design, might rethink it, in the meantime any examples or pointers appreciated.
Ihey there, I get a 525 error when I try to use the DeepL API from my worker. It works just fine locally and the issue only appears once deployed to production. From researching its got something to do with the SSL handshake between CF and API but I havent found a solution, anyone know how to solve it?
Jthanks @Leo I'll give it a try later today.
CHi. I'm trying to build a CF worker-based solution to create large zip files and looking for some advice.
I need to zip hundreds of few-MB files located in R2 into zip uploaded to R2. Resulting zip can be ~1GB which is way over worker memory limit so I had to stream zip into buffer and upload chunks using r2 multipart upload.
The problem is that both http fetch and queue consumer event are limited to 30s of cpu time, which causes cpu exceeded error usually around 500MB of processed zip data. I'm trying to improve the task to be able to recover from being terminated at any time (with queue retry) but it's non-trivial to resume original state of things.
Maybe using workers isn't the right choice for this task. Does CF have anything better suitable? Thanks!
I need to zip hundreds of few-MB files located in R2 into zip uploaded to R2. Resulting zip can be ~1GB which is way over worker memory limit so I had to stream zip into buffer and upload chunks using r2 multipart upload.
The problem is that both http fetch and queue consumer event are limited to 30s of cpu time, which causes cpu exceeded error usually around 500MB of processed zip data. I'm trying to improve the task to be able to recover from being terminated at any time (with queue retry) but it's non-trivial to resume original state of things.
Maybe using workers isn't the right choice for this task. Does CF have anything better suitable? Thanks!
AI'm not sure your use case or how scalable it needs to be, but if you only need to run it once per hour (or less), then cron triggers can use up to 15 mins of CPU time (more frequently than an hour and it's 30 seconds)
C@Ashley unfortunately cron is not an option for me. it needs to execute on demand.
DThere's some use cases that just aren't going to be a good fit for the (current) Cloudflare offerings. This might be something you have to do on another compute platform.
DI've been moving various things from AWS to CF myself, but some things are staying at AWS (for now) due to their requirements just being a better fit for AWS solutions.
HVia a WebSocket?
HAt least afaik returning a Reaponse while still receiving a Request is against the HTTP Spec
