Is there a limit to the total number of live past deployments on Pages?
Is there a limit to the total number of live past deployments on Pages?
MHi Rachel, mind retrying your build?
MGlad it works, we pushed out a fix for the issue you were having, earlier today
JI've hit day 5 of not being able to publish new content. I keep getting the following very generic error message when publishing to pages, can anyone help debug?
I
Wwhat's the deployment ID?
Walready here Isaac :p
Icebd1750-f1b4-4fed-99d2-71c7398730
Wdid you just ocr that?
IYeah 
Wsmart
I
J(thanks, stepped away for a few minutes and missed the message)
WThis is an issue with the new uploader, seems like you have some large files and it's causing memory issues. I'll take a look at improving our memory efficiency on Monday
JThanks, not sure if it helps debug the issue but there are lots of small files, I don't believe there's a single large one.
Wwhile this could happen with lots of small files, I wouldn't really expect it. I see you have 50+ images, what are the sizes on those?
JThere are 3 that are around 1.3M, the rest are around a couple of K, none of those are new though
Wis your repo oss?
Jit's a private github project
JNice! I've been enjoying Remix with Pages.
MJust wanted to bump this Q.
MShould i be deleting my old deployments to avoid hitting some kind of soft limit?
CIs the private module on npm? I know there is this guide for installing from npm https://developers.cloudflare.com/pages/how-to/npm-private-registry/
Documentation for Cloudflare Pages, the best way to deploy your static and JAMstack sites
CThere is nothing listed on the limit section (https://developers.cloudflare.com/pages/platform/limits/) so you shouldn't need to worry about deleting old deployments
Documentation for Cloudflare Pages, the best way to deploy your static and JAMstack sites
HAFAIK, no, though it is always a good idea to delete deployments you no longer need(save the environment!). But, as long as you aren't abusing the feature or storing millions of old deployments, you should be fine.
AIs there a way to nuke API keys and other credentials for Pages and generate new ones?
I'm investigating possibility that one of our Pages API keys + account id had been leaked. Trying to determine if the only option is deleting site and redeploying.
I'm investigating possibility that one of our Pages API keys + account id had been leaked. Trying to determine if the only option is deleting site and redeploying.
HYou mean your regular CF Account API Credentials, or…?
ANo specifically keys from the API section under a page. Like account id and API token
Aone is account id that shows up under the bottom of this screenshot
Aunder Zone ID
WYou can't change your account ID but that isn't sensitive
WIt just identifies your account
WWith an API token or API key you could still grab an account ID
WSo if you've leaked one of those best thing to do is roll it (and also not leak again :p )
Dand also not leak againsaid
Anpm i -g leakless strategy
HSo what you’re saying is…
HDon’t pull a you?
W
CIf you are checking out a repo you can pass an oauth token to autehnitcate. ie
git clone https://oauth:<your PAT Token>@github.com/...Wthat requires ssr
