We’ve been seeing weird caching issues and I’ve been told on here you need to bypass zone caching on
We’ve been seeing weird caching issues and I’ve been told on here you need to bypass zone caching on a Pages app
SIt isn’t documented yet, I need to put in a feedback request on it. I’m sure behind the scenes the pages team is doing all sorts of magic with other Cloudflare products, we just need to figure out what the best practices are
CThe recommended way is to have your framework minify the output but otherwise you can use your zone level minify settings to do it
DI have a (next on) pages site that uses Firebase + the firebase client sdk for some file serving, and we pay a not pretty amount of money to Google for the bandwidth. Google has special pricing for being accessed by CDN networks but I don't know how to... do that... with my setup.
DI've had a few ideas but they've all hit random dead ends, most notably my idea to just move to R2 lol
DWould love some help brainstorming 
DIs there a way to see the traffic information (unique visitors, total requests, etc...) for the pages.dev site directly for static webpages? Just like we can see in the "Analytics" tab for a standard website handled by Cloudflare. I know it can be done by using custom domains or that there's more detailed information by using the Web Analytics and setting up a beacon, but I'm just looking for a short, no setup needed overview of the traffic.
DSearched around a bit, but I haven't seen that question asked anywhere yet.
HIf you go to Project Settings, hit
Enable Web Analytics, then redeploy your project, it should inject the Web Analytics Beacon for you automagically.
MIs anyone having issues with automatic deployment from GitHub?
MI sent changes in two different repositories and the deploy didn't happen...
BLooks like Github actions / api is down/having trouble right now, are cloudflare pages builds also failing for others for the same reason
Uas long as webhooks and git ops are still working which the status page seems to indicate they are then pages should still be building just fine assuming you have a project that uses the git integration
Uthe status page could also be entirely wrong about the severity of the outage though
Ufwiw though pages builds with git integration works fine for me right now
GHey Greg, any movement on this? Would be great to have it configurable. Some section of my build tool is exporting to a
node_modules
SMy Pages project wasn't deployed after I pushed to the master branch 15 mins ago. That never happened to me before.
Previous one (22h ago) was ok.
Previous one (22h ago) was ok.
EHey we're currently having some issues reported here: https://www.cloudflarestatus.com/incidents/mbwnmsh71p98
Could you try again later once the incident is resolved?
Could you try again later once the incident is resolved?
SGreat, thanks. Will try again later then.
By the way, I pushed once again and this time deployment went well.
By the way, I pushed once again and this time deployment went well.
EThis is likely to be unrelated, but does indeed look weird!
V
Hi everyone, @945732495889014814 
team is excited to introduce build cache - a feature designed to speed up your build times by caching and reusing previously computed project dependencies and build outputs 
This is a very early version of the feature, and while we're excited about its potential, we recommend not enabling it on critical projects just yet. Please note that the Build Cache feature will support Next.js and Gastby.js, and the package managers npm, pnpm, and yarn v1. Users who opt-in will have their project's build image setting overridden to a beta version of the v2 image.
If you have projects that meet these requirements, then please feel free to sign up via this form: https://forms.gle/wTpVpJNFkAR84TMd9. Your feedback will be crucial in shaping the future of build cache. Thanks for being on this journey with us!
If you have questions or feedback please use the channel build-caching-beta
KTake a lurk into the security logs and if it is something that blocks it but it's needed then create a rule and disable it on the domain
K*That's how I did it on my postgre, MySQL MS and with Matomo
HI don’t think they have access to the dash.cloudflare.com zone…
KUh okay i thought everything that is related to the domain
KHey! I have pages project which must include itself a bunch of reports (few servers tests in single html file each). i want to have smth like in root path list of all folders near root index.html and when u click each - u go to the this directory (change path) and see the report. problem is how to display a list of folders, cuz when i deploy project with non existing root index.html - i get 404, but all the subfolders are opening. Is it possible to do some with this?
Wnewbie question: If I wanted to use authentication on my web app on pages, are there any good tutorials or docs for this? Like, when running web apps that allow Google OAuth2 login, there are libraries and such to help set up all the connections required for auth. Any help or links to resources is appreciated. :). (I tried to search for it, but either there isn't much out there OR I'm just not using the right search string.)
WMy assumption is that I'd use a Worker to protect the routes served by pages. but even there, I'm clearly missing something obvious in my search OR this just isn't something people do OR it's not really an option given how OAuth2/Workers function.
TRecently we have been getting 8000000 errors when deploying pages from github actions with https://github.com/cloudflare/pages-action
TJudging by the forums I am not the only one:
https://community.cloudflare.com/t/code-8000000/554254/5
https://community.cloudflare.com/t/code-8000000/554254/5
AYup it's happening for me as will. pages-action started failing in CI
AIs this the correct place to raise the issue? We need some deployments to go out and this is a hard blocker it seems. I'm assuming it's broken for almost everyone?
I tried to run deployments manually via the wrangler cli and it didn't work.
I tried to run deployments manually via the wrangler cli and it didn't work.
ZAHmm I don't think it get's to the deploy step. Here is the output for me
ZAh, so this only seems to happen when deploying with Wrangler?
AThings to notice
- It took 95 seconds to upload assets, that is VERY unusual
- Even in CI, it gets to the same spot and fails. Tldr the whle process takes very long and then fails at the end
AI don't really use the pages github connection so I can't say for sure if that's working or not
AAll my deployments run through
pages-action on github (which is basically the wrangler cli)ZOkay, let me quickly see if I can reproduce it. What version of wrangler are you running?
A3.7.0AActually, interesting update, I followed the recommendation on one of the community posts, running
wrangler logout and then wrangler loginOdd 