yeah, it did seem like you could get pretty far with that!

the one rule limit is kind of restrictive though

probably enough though when I think about it

can durable objects not have cron triggers?

They have something similar called alarms, which are actually more precise, but you have to schedule it every time

No, but they can have Alarms

ha, got you

yeah, just would be nice to have the simplicity of cron triggers you could twiddle in the dashboard

cries in non-colored dev expert

curious if it's something that's planned

I mean, you can pass Cron Triggers into a DO

Probably not. You can pass them in if you need them, or otherwise build your own with Alarms

get yer hands dirty

There’s not really much of a need that doesn’t work there

I'm kind of surprised there aren't more abstractions built on top of DOs

oh wait of course, there's do-taskmanager!

and

do-transactional-outbox

has anyone made a cloudflare worker / DO resources cheat sheet github repo or something?

with all these things linked

itty-durable, do-taskmanager, do-transactional-outbox..

Not sure where to log this bug but AFAICanTell DO local encoding for keys is creating folders instead of files in memory and causing errors when colons exist in strings.

// npx wrangler dev --local # MacOS wrangler 2.12.2
do.storage.put({
  'this:that': 0, // becomes a directory in /private and throws errors on future delete / access
})

That looks like a miniflare bug

Hey team, I removed one DO call and one Queue call, my api response time down from ~1200ms to ~350ms. When I just remove addRefreshToken method which puts to Token Do, reduce the latency to ~680ms. Is this expected? I mean internal DO calls take ~500ms? and queue call adds ~300ms?

ts
const promises = await Promise.all([
  userClient.createSession(applicationInfo, sessionId, refreshToken),
  /* 
  addRefreshToken(c, refreshToken, sessionId, userId),
  c.env.AUTHC1_ACTIVITY_QUEUE.send({
    acitivity: "LoggedIn",
  }), 
  */  
]);

Hello. I'm having trouble finding instructions on how to use a Durable Object in a separate Worker in local development. I am running both instances at the same time, but my Worker says "DurableObjectError [ERR_CLASS_NOT_FOUND]". How is this supposed to be set up?

Have you followed the guide here? https://miniflare.dev/storage/durable-objects You also need to make sure the DO are exported from the main CF entry point

Isn't miniflare part of wrangler? Do I need to install miniflare separately, or what? Seriously, this is so confusing...

"Ignored: "miniflare": Wrangler does not use configuration in the

miniflare

section. Unless you are using Miniflare directly you can remove this section."

I did get a separate Durable Object Worker to work locally together with a Pages project, by using the

--do

flag, but it's not available for Workers for some reason.

So how do I access a Durable Object locally from another Worker, without

--do

or

--do-persist

?