I'm going to DM you so we can keep troubleshooting there, both so we don't pollute the main thread of the channel but also so I can ask more about your particular Github config
Is there any difference between pages functions and a standalone worker? I've use used pages with functions but now i just need a small api (without static content/frontend) should i go with workers or i could just make a pages project and uses functions?
Functions by default has file-based routing which is nice, but it tends to lag behind Workers in terms of new features (like Logpush or Hyperdrive bindings)
I’m building a cloudflare pages plugin that will host an admin like interface. the only way to “define” an api for it is to continue adding path based handlers as part of the middleware itself?
weird question, on a monorepo, in the packages folder where I’m developing my cf pages plugin, is it possible to make the plugin serve the dist of the nextjs compilation? Or I’m forced to construct my response on the fly?
basically trying to understand if its easy to develop that way so that users control and host their own admin interface, or if the plugin should only expose my api and on login to an external admin, communicate with the pages that have the plugin added