hi, hi. Could you please try going directly to https://github.com/cloudflare-pages/installations/sel

hi, hi. Could you please try going directly to https://github.com/cloudflare-pages/installations/select-target to see if you can configure your Github settings for your Pages project from there?

Aale hi, hi. Could you please try going directly to https://github.com/cloudflare-pag...

ayamg0r3ng•10/10/23, 2:22 PM

Copy the url? and run it? the result still going to 404 page

ayamg0r3ng•10/10/23, 2:22 PM

is this what u mean?

aleOP•10/10/23, 2:23 PM

yes, indeed

aleOP•10/10/23, 2:23 PM

and I'm assuming you're logged into your Github account, right?

Isaac McFadyen•10/10/23, 2:23 PM

Are you definitely signed in?

aleOP•10/10/23, 2:23 PM

lol

ayamg0r3ng•10/10/23, 2:24 PM

yes

Isaac McFadyen•10/10/23, 2:24 PM

Sorry, I'll stop interrupting lul

ayamg0r3ng•10/10/23, 2:24 PM

I log out still like that

ayamg0r3ng•10/10/23, 2:25 PM

that I already do it before, if I log out. just going to sign in page after that going to 404 pages

ayamg0r3ng•10/10/23, 2:25 PM

wait let me replicate

ayamg0r3ng•10/10/23, 2:27 PM

after sign in going to 404 page again

Aale yes, indeed

ayamg0r3ng•10/10/23, 2:29 PM

I already do it. sign out from cloud flare and github. and try it again, the 404 page still happening

aleOP•10/10/23, 2:33 PM

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

AAlberto Abruzzo downloading nodejs

itsmatteomanf•10/10/23, 5:21 PM

Yeah, it sometimes happens... I have been pushing for NodeJS caching

AAlberto Abruzzo i think the nodejs repo has problems

itsmatteomanf•10/10/23, 5:23 PM

Yeah, I know it's on NodeJS' side... it's their caching infrastructure that's not really optimised NotLikeThis

FredSchmitz•10/10/23, 6:09 PM

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?

kian•10/10/23, 6:16 PM

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)

kian•10/10/23, 6:16 PM

If you want to go with a Worker, look at a framework like https://hono.dev

agathorpt•10/10/23, 6:17 PM

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?

agathorpt•10/10/23, 6:25 PM

lol just saw honov3 supports cf pages, guess I’m going to give that a try

Kkian If you want to go with a Worker, look at a framework like <https://hono.dev>

FredSchmitz•10/10/23, 6:26 PM

Thanks! I will look into it

AAlberto Abruzzo Click to see attachment

JohnDotAwesome•10/10/23, 7:58 PM

FWIW, if you can use the latest version of node 16 (16.20.2), you can simply express

NODE_VERSION: 16

NODE_VERSION: 16

in your environment (or 16 in node version files) and it won't have to download anything

agathorpt•10/10/23, 9:06 PM

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?

agathorpt•10/10/23, 9:11 PM

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