Cloudflare Developers

CD

Cloudflare Developers

Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news

Join

Does it need to happen synchronously,

Does it need to happen synchronously, before the HTTP response ends? If not, you could use Workflows and do batches of 100 and then a sleep. Alternatively, you could use Queues and publish a message per item and have some rate limiting, but Workflows will be better imo. Only drawback will be you’d need to create sub Workflows at a certain point with the current step limit (e.g. you’d have an effective cap of 51,200 inserts per Workflow)

@thomasgauvin , I posted a question

@thomasgauvin , I posted a question about hyperdrive on local a little earlier

Also, I'm having trouble connecting with

Also, I'm having trouble connecting with a local postgres DB when using hyperdrive. I've tried both using the env variable & the localConnectionString, but I keep getting this error: ```...

Workflows result

👋 Is it possible to get a result from creating a workflow? Something like this? let result = this.env.MYWORKFLOW.create({ params: { id }, })...

I am, its working pretty good. The

I am, its working pretty good. The durable object isn't that big of a cost factor if you use it at scale. Maximum like $10 dollars a month orso? That you use it like 24/7. As currently there are not session costs?

What's your payload?

What's your payload?

^ I believe I've found a bug with

^ I believe I've found a bug with Workers CI/CD, what's the best place to report that? (I was able to reproduce the issue, and it seems related to my setup and how Workers CI is triggered)

and I guess Prom in a DO means saving

and I guess Prom in a DO means saving the state of a counter in the DO 😅

does snippets support kv? If not is

does snippets support kv? If not is there any plan to add this support?

Workers as your fallback origin | Cloudf...

When your setup is like: subdomain.customerdomain.com -> fallback.domain.com, Worker Routes sees the incoming request as "subdomain.custerdomain.com/" and thus fallback.domain.com/* wouldn't match. You need a wildcard as per this guide: https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin/ just be careful to exclude your own subdomains first or use a dedicated domain/zone for cf for saas...

Thread

Do you mind if I DM you a few questions?

adding assets to workers is sick and i'

adding assets to workers is sick and i've got it working. but not_found_handling = "single-page-application" doesn't seem to quite work without handling in the worker? Am i right about that? You want to bind it and hand the request back to assets to get the correct asset.

Workers Builds! 🙌 can't seem to get Bun

Workers Builds! 🙌 can't seem to get Bun working though... even tried setting BUN_VERSION build env var, tried .tools-versions. Anyone get this working? Also a retry button on failed builds would be very helpful!
No description

Trying out the new workers with assets.

Trying out the new workers with assets. Just initiated a solid-js project as described in the tutorial and deployed. Looks like static assets aren't cached by default Cache-Control: public, max-age=0, must-revalidate. How do I configure the worker with a proper cache-control header for hashed static assets built by the framework?...
No description

Slight bug with new worker CI/CD: adding

Slight bug with new worker CI/CD: adding a root directory for the worker in the inital drawer page doesn't work, it goes back to / after you create the integration. Editing it afterwards works fine.

Workers should be fine - got anymore

Workers should be fine - got anymore info?

I've been following along with the

I've been following along with the commits in the workers-sdk repo for the new experimental-assets. Played around with it a bit in a small repo. It is so close to providing the perfect developer experience for building sites on workers. The main feature I would love to see is support for running wrangler dev and having vite live reload the browser whenever I make changes to my HTML, CSS, JS that runs through the worker. You would get the best of both worlds, (quick update in the browser when you modify your code/you are actually running your app via the worker so its more true to how it will work in production). You can get live-reload partially working with workers + assets, but really what I want, and I'm sure many others want is full integration with wrangler dev and vite to do real hot module reloading. It feels like this is possible with the new Environments API in the latest Vite beta but I havent dug in. Is the team that is working on the new experimental assets thinking about any vite integration that would support HMR/live reload with workers? If not, what's the best way to pass along that use-case, open an issue on the workers-sdk repo?...

Given Workers now supports building

Given Workers now supports building within Cloudflare instead of your own CI pipelines, are there plans to support build caches similar to Pages? I haven't had a chance to speedtest it but Workers Builds seems to be much slower than using GitHub Actions and Pages as it's re-downloading every package each build Ref: https://developers.cloudflare.com/pages/configuration/build-caching/#how-build-caching-works...

what is the status for this synchronous

what is the status for this synchronous XHRs?

Sorry for the question, I was searching

Sorry for the question, I was searching for help respect a problem I have with my IP and it seems that Cloudflare is involved, is there a channel where I can get any help with it? or it is mandatory to send an email to the company?
Next