My issue with using the Supabase client is that it's HTTP like you said, I can't use transactions wh
My issue with using the Supabase client is that it's HTTP like you said, I can't use transactions which is pretty much a requirement
KThe
pgnode_compat
CUnfortunate that pages can't run node_compat. If you're needing transactions but still want to use the supabase database for sure, neon's serverless driver is able to run on any postgres database, as long as you run their websocket proxy for your edge clients.
E@kian Ah I have been running
wrangler pages dev ./public --compatibility-flags=nodejs_compat - although, in the dashboard for pages it does allow you to set that?
Knodejs_compatnode_compatnode_compatpgnodejs_compatnode:Well TIL I didn't even notice that
Kpages dev--node-compatpages deploy doesn'tKso uh, I don't think it's usable in production
EI get
service core:user:worker: No such compatibility flag: node_compat
EI'm not requring supabase, the main thing is being able to run transactions (via code) from Pages on a database:
So any SQL DB would be ok, I'm just trying to connect at the moment
I've been using Prisma which is great, but their data proxy reguarly hangs, and their support is slow and not helpful
So any SQL DB would be ok, I'm just trying to connect at the moment
I've been using Prisma which is great, but their data proxy reguarly hangs, and their support is slow and not helpfulEI either get cold starts (on their service) or timeouts
CI see, I'm about to head to bed, but I was googling to learn more about the different drivers just now and it seems like neon's driver in drizzle would be the most seamless switch for you. Neon's driver uses websockets as an alternative to native pooling or http, which means transactions & edge compatability ! Haven't used it before but they seem to be making lots of people happy, and were super nice with their pre-launch contact so I'd say give it your best shot!
CCan't wait to see how it turns out for you
EThanks, really appriciate it
KYeah, it isn’t a compatibility flag
KIt’s a separate wrangler feature that Pages doesn’t support
HBecause Pages uses its own cache which afaik doesn’t show up in Cache Analytics
HIt may make it slower for Pages to update after a new deploy occurs
Anot entirely sure how to ask this question, but i'm generating pages projects via API and it is not clear to me how i connect a pages project to a github repo
there is a source key, but there's no docs on how to use it
there is a source key, but there's no docs on how to use it
Ai've taken a look at how wrangler does it, looks like it's using a short sha- but if so, still not clear how that is associated with a github origin/repo
HOnce a project is created, then you cannot attach it to a GitHub/GitLab repo. You have to create a new project, then connect it there
Aso i am trying to create a project, attached to a github repo, via the API
Ajust asking how to do that
AHAs far as documented APIs go, you can create a project via the API, but you cannot connect it to a Github repository.
Ais that because it's not possible or because it's just not documented?
Ae.g. d1 apis aren't documented but also exist
HYou can do whatever the Dashboard does to create a project
HThough I definitely wouldn't count on them being stable enough to rely on
Athat's ok for us imo
Ais this consumable in a form that isn't the browser inspector by chance?
HWdym?
Ai just mean has someone else done this and kinda sketch how to do it
Ainstead of me going in and figuring it out
HI don't think so. If you don't want to inspect the Network tab directly, then you would have to reverse the Dashboard browser bundle, which would take a while.
Akk
Ais this something that is facilitated better by the platforms program?
HMaybe? It has more API-support, but no Github/Gitlab support at all
Anods
Aappreciate your time!
BApologies if this is any easy thing but i couldn't find an answer when searching
I have a cloudflare pages app (remix app) that uses KV. Using wrangler 3.5.1
When running locally
I have a cloudflare pages app (remix app) that uses KV. Using wrangler 3.5.1
When running locally
wrangler pages dev ./public --kv STORE i would like to:- access my production KV values
- pre populate the local sqlite db with values from my production KV
.wrangler/state/STORE/:id. Is there an equivalent way to do that with wrangler 3.x sqlite? Or more ideally to use the production data from the remote KV?
BOut of curiosity, when visitors request a page for my site (which is running on Pages), is the response built from data in the internal KV store every time or are responses cached as well? I'm sure the difference is a negligible <1ms, but I was pondering.
BI'm not sure the high-level details of how Pages works are documented anywhere (although perhaps Workers Sites was at one point).
CYou can use
wrangler kv put --local --binding STORE <value to add to local KV