feat: implement durable objects for editor page

[leonardcser]

No description provided.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	dafthunk-web	ffd5c0b	Commit Preview URL	Oct 07 2025, 08:15 AM

[leonardcser]

@bchapuis The individual ws implementation is complete but the api build fails. We would need to check the logs of the failed api build and enable maybe durable objects, or create the durable object in the cloudflare account. Otherwise, this PR is ready to merge

[bchapuis]

@leonardcser Here is the log:

18:14:47.127	✘ [ERROR] A request to the Cloudflare API (/accounts/ad4c9e9945d2de46a4dfe2bd179fdc63/workers/scripts/dafthunk-api/versions) failed.
18:14:47.127
18:14:47.127	Version upload failed. You attempted to upload a version of a Worker that includes a Durable Object migration, but migrations must be fully applied by running "wrangler deploy". See https://developers.cloudflare.com/workers/configuration/versions-and-deployments/gradual-deployments/#gradual-deployments-for-durable-objects for more information. [code: 10211]
18:14:47.127	To learn more about this error, visit: https://developers.cloudflare.com/workers/configuration/versions-and-deployments/gradual-deployments/#gradual-deployments-for-durable-objects
18:14:47.127

Does this ring a bell?

[leonardcser]

Does this ring a bell?

@bchapuis I think you have to run in apps/api pnpm wrangler deploy to create the migrations for the Durable Object as per the docs (https://developers.cloudflare.com/durable-objects/get-started/#7-deploy-your-durable-object-worker)

[bchapuis]

@leonardcser I made some additional experiments in #172 and started implementing the monitoring of the execution with the websocket.

I encountered the following problems:

• the ws cannot register a callback in the runtime and needs to poll the state out of the db (this is undesirable)
• queues would be a good solution for this, but they don't provide a to filter the messages related to the workflow of a user
• the documentation recommend pub/sub for this use case which now recommend actors which are implemented with durable object... 🤯

I'm now again of the opinion that we should use durable objects with actors for this particular use case. What do you think?

I suggest we build upon your last commit.

[leonardcser]

@leonardcser I made some additional experiments in #172 and started implementing the monitoring of the execution with the websocket.

I encountered the following problems:

• the ws cannot register a callback in the runtime and needs to poll the state out of the db (this is undesirable)

• queues would be a good solution for this, but they don't provide a to filter the messages related to the workflow of a user

• the documentation recommend pub/sub for this use case which now recommend actors which are implemented with durable object... 🤯

I'm now again of the opinion that we should use durable objects with actors for this particular use case. What do you think?

I suggest we build upon your last commit.

@bchapuis It is still unclear for me if it is possible with this actors API, I need to do more exploring but in the meantime, it makes sense to commit to this pr.

[bchapuis]

@leonardcser Could you review these changes? we decide upon merging later this morning.