Comment by buremba

1 month ago

I tried to run it locally some time ago, but it's buggy as hell when self-hosted. It's not even worth trying out given that CF itself doesn't suggest it.

4 comments

buremba

Reply
ketanhwr  1 month ago

I'm curious what bugs you encountered. workerd does power the local runtime when you test CF workers in dev via wrangler, so we don't really expect/want it to be buggy..

  • buremba  1 month ago

    There is a big "WARNING: This is a beta. Work in progress" message in https://github.com/cloudflare/workerd

    Specifically, half of the services operate locally, and the other half require CF services. I mainly use Claude Code to develop, and it often struggles to replicate the local environment, so I had to create another worker in CF for my local development.

    Initially, the idea was to use CF for my side projects as it's much easier than K8S, but after wrestling with it for a month, decided that it's not really worth investing that much, and I moved back to using K8S with FluxCD instead, even though it's overkill as well.

    • kentonv  1 month ago

      > There is a big "WARNING: This is a beta. Work in progress"

      Ughhhh that is because nobody ever looks at the readme so it hasn't been updated basically since workerd was originally released. Sorry. I should really fix that.

      > Specifically, half of the services operate locally, and the other half require CF services.

      workerd itself is a runtime for Workers and Durable Objects, but is not intended to provide implementations of other services like KV, D1, etc. Wrangler / miniflare provides implementations of most of these for local testing purposes, but these aren't really meant for production.

      But workers + DO alone is enough to do a whole lot of things...

      1 reply →