Hacker News Reader

Comment by orkj | Hacker News Reader

Genuinely curious: does this mean you can run WordPress as a cloudflare worker (ignoring database for now)? https://developers.cloudflare.com/workers/runtime-apis/webas...

View on HN

The team behind this tried to deploy to Cloudflare but hit memory constraints with Workers due to the 128MB limit there:

https://github.com/WordPress/wordpress-playground/issues/69

There’s likely more work that could be done to make this viable, though (or Cloudflare could raise limits).

So what's the min limit required to make it run?

They estimate ~155MB just to get PHP running in Workers. It will be more to load WordPress. And there is extra work to get it running with Cloudflare D1. Plus everything else that likely won’t work by default there (e.g. image uploads).

Note sure, but I like how you think.

there is this: https://ma.rkusa.st/store-sqlite-in-cloudflare-durable-objec... and this: https://developers.cloudflare.com/d1/

So I'm thinking it could (be made to) work.

I did know of those, I'm just assuming its going to cause some sort of problem with network calls and sockets and what not (they mention this specifically as part of the caveats)

Replying to myself. I guess I read that a bit too quickly:

> In Node.js, the answer involves a WebSocket to TCP socket proxy, Asyncify, and patching deep PHP internals like php_select. It's complex, but there's a reward. The Node.js-targeted PHP build can request web APIs, install composer packages, and even connect to a MySQL server.

Hm, that sounds very interesting and promising

Reply on news.ycombinator.com