XThank you for pointing this out, I'm implementing this right now
XI'm running into an issue where trying to use AWS SES within pages does not work. A runtime error occurs:
Error: Dynamic require of \"node:buffer\" is not supportedXIs there any way around this? I dont want to use other services like mailgun because they're way too pricey 
JThis is what I am currently doing to connect to a postgres db from within pages using the pg driver
1) Create a pages application, for mine I am using Remix.
2) Setup a worker called
3) Setup drizzle with an http proxy in your pages application. The pages app can use a service binding to call the
4) Make requests with drizzle, they will be proxied to your pages worker and your pages worker will use the connection pool from Hyperdrive.
With this setup you can connect to any postgres db.
For email using Amazon SES I was able to get @aws-sdk/client-ses working within a pages handler.
1) Create a pages application, for mine I am using Remix.
2) Setup a worker called
pg-proxy that has a binding to a Hyperdrive instance. Use the Hyperdrive connectionString with the pg driver in the worker.3) Setup drizzle with an http proxy in your pages application. The pages app can use a service binding to call the
pg-proxy worker directly.4) Make requests with drizzle, they will be proxied to your pages worker and your pages worker will use the connection pool from Hyperdrive.
With this setup you can connect to any postgres db.
For email using Amazon SES I was able to get @aws-sdk/client-ses working within a pages handler.
AHi, I am using Cloudflare Turnstile captcha for my website. sometimes the captcha works but sometimes even if with the genuine user the captcha fails and returns error, not allowing user to do the payment. Please guide me on how to fix this ?
Nhow do I set node_compat for my page in dashboard?
N
NI am not sure it's this
HPages doesn't support
node_compat. It does support nodejs_compat, which is slightly differentNhow do i set
nodejs_compatN
Nactually i have it set
Nit seems
IHi Cloudflare, do you have policies on .dev pages where phishing sites are swarming?
FIf you feel that a site is engaging in illegal or inappropriate activities, you can submit an abuse report at https://abuse.cloudflare.com/. The Trust and Safety team will review the details and reply if appropriate. You can also report the site to your relevant local authorities. Reports cannot be filed via Discord or with individual employees or Champs.
IThese are the phishing pages, I wonder what is your turnaround time for these? We already used your CloudFlare abuse forms, and it seems there are no actions
HWe can't do anything here. All Abuse-related actions can only be handled via the abuse form.
Ithanks 
IAnd when that won't work, who can we talk to? how do I even know if they are looking at my reports?
HThey are the only ones that can handle those reports
HThere isn't anything else we can do from here
SIs it possible to move the git repo ownership without impacting the page app setup?
XThank you for suggesting 
@aws-sdk/client-ses, it seems that aws-sdk (the lib i was using) is old and will be depricated next year. Everything works fine now 
AHello, does Cloudflare Pages support SSR sites? is using a lite node? or full node compatibility? I saw some posts that users complain that some packages don't work because the less node compatibility.
ICloudflare Pages supports SSR, but it's not Node - it's the Cloudflare Workers runtime, which is a lightweight JavaScript runtime that supports a smaller subset of Node features.
IQuite a few things work, especially with Node.js compatibility mode enabled, but some don't (e.g. there's no filesystem so no
fs)IThe only way to know for sure is to try it out with your specific use-case.
Athank you @Isaac McFadyen
JYeah been this way for a while. Definitely use the v3 libs
MWhy not point the domain there directly? What should the custom domain be used for if it doesn't point there?
DI was using git integration, for some reason I needed to use GitHub actions to build my pages project and deploy it using pages action. So I deleted the project and re-created it so I can use assets upload. But when I try to add my custom domain it says:
CDo you have any unpaid/partially paid invoices? iirc the billing migration has been messing with that a bit as well.
Otherwise you'll need to email that abusereply@ address
Otherwise you'll need to email that abusereply@ address
DNo, I sent an email.
Thank you.
Thank you.
DI didn't get the reply yet, if I don't know the problem how can I fix it. And what if the site was production ready, I may have lost many traffic?
SAnyone know if build caching works with remix projects or if there is way to leverage it unofficially? Its not in the documented frameworks.
Jif a domain
Can
example.com is a Cloudflare Zone inside Account ID 1, and a Cloudflare Pages project exists for Account ID 2. Can
example.com (the apex) be added as a Custom Domain on the Pages project? Or do you need to actually own the zone / have access to the zone for it to work?
WYes but you may need to use the API/Terraform
WThe UI will not properly see it and will say to move to cf
Jhey Walshy! thanks for such a quick response. Got it! That makes sense, didn't know there was an API, that's actually even better
PCan someone check my thinking here, I'm a bit confused by how I should configure my
I'm a bit confused about how this should be configured for local dev. When I run
When I want a miniflare D1 DB local for dev, should I be changing the
I'm a bit more confused trying to understand the
With the actual ID:
With the string "DB":
Why are there two listed here? Why are they both the same in the first scenario? Both bindings are set to "DB", and that's how they're referenced in my functions.
I have the impression that my
wrangler.toml to account for the fact that I have a Pages app, a production database, and a preview database. The prod and preview DBs are bound to their respective environments via dash app as "DB".I'm a bit confused about how this should be configured for local dev. When I run
wrangler pages devWhen I want a miniflare D1 DB local for dev, should I be changing the
wrangler.toml to not have the actual preview_database_id and replace it with just "DB"?I'm a bit more confused trying to understand the
wrangler pages devWith the actual ID:
With the string "DB":
Why are there two listed here? Why are they both the same in the first scenario? Both bindings are set to "DB", and that's how they're referenced in my functions.
I have the impression that my
wrangler.toml is correct because my CI migration wrangler d1 migrations apply with and without --preview appear to be running on the expected DBs. I'm just still quite a bit confused about how this should be set up for local dev. I could maybe use a separate .toml file for local dev? I could try to remember to change the file each time I want to work locally? Maybe I'm missing something?
Thow do i make
Cache-Control to have these status ? private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Cache-Control to have these status ? private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
AQuestion, I see a bunch of lines in the recent wrangler release notes on Pages support
wrangler.toml. Is there experimental support for this already? Any docs or tips on how we can use this?
CI don't believe that the wrangler.toml works yet on deploy
W^ still in the works
Wwe'll make sure to announce when it's ready to test 
AIn the docs for pages limits, is the 20 MiB limit per file or per site?
