Should i be deleting my old deployments to avoid hitting some kind of soft limit?
Should 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
Was soon as we have that yes
Wnext team are still working on their switchable runtime
Wonce it's in a stable state we're good to go (in theory - in reality there's still a bit more work to be done but yeah)
SIs cloudflare pages suffering from some performance degradation?
Jwhere exactly? There was some general issues in LHR earlier today: https://www.cloudflarestatus.com/incidents/qg70r72v0qll
Sits gotten a lot better now, pages were really slow before and some images failed to load
it might be a problem on my end
it might be a problem on my end
Rdoes anybody know how SvelteKit Endpoints are being billed? they don't show up at workers or page functions... am i missing something?
IThey are Pages Functions.
ISvelteKit builds to Functions (a single monolithic Function).
IFunctions aren't being billed yet, but every request, even static assets, counts towards your 100k Functions quota.
ROuh
R
Rim confused cause normally the functions show up here
KIf it was with wrangler's Direct Upload then the UI is currently bugged (Functions/Redirects/Headers don't appear despite being there)
KI don't actually know if
_worker.jsOuh okay that makes sense... i was worried i get banned for abusing a bug or something
IYeah, it doesn't.
EIf you upload a folder from your browser and publish your site, just edit your local index.html and upload the updated folder from the "Create a new deployment" button.
EWhen I looked at the site I uploaded to pages, I noticed that
I don't want this, so I tried adding the
I plan to use CI in the future, but for now I'm manually uploading the directory. I uploaded a directory containing the _headers file and it seems to be deleted.
What should I do?
access-control-allow-origin: *I don't want this, so I tried adding the
_headers file to remove this header.I plan to use CI in the future, but for now I'm manually uploading the directory. I uploaded a directory containing the _headers file and it seems to be deleted.
What should I do?
WYou should still have the file locally. Edit that and then re-upload the site
WI don't think the dashboard supports _headers right now. If you use wrangler you are good
EI tried publishing using wrangler, but _headers seems to be ignored.
I can't find _headers by looking at the uploaded files in the dashboard.
I can't find _headers by looking at the uploaded files in the dashboard.
Ehttps://github.com/cloudflare/wrangler2/issues/1215
This seems to be the intended behavior. And the same goes for not appearing in the headers tab of the dashboard.
But my site still gets
This seems to be the intended behavior. And the same goes for not appearing in the headers tab of the dashboard.
But my site still gets
access-control-allow-origin: *The root directory of the deployed folder.
When deployed with
When deployed with
wrangler pages publish .\dist\client\, it was in .\dist\client\_headers