Why Cloudflare decided to use LE for Pages sites?
Why Cloudflare decided to use LE for Pages sites?
IWould you mind sharing a screenshot of the DNS record(s)? If it's on Cloudflare it's normally auto-configured, even though it doesn't mention it (cc @albertzhao).
IProbably faster to issue? Not really sure... they are available also for non-Pages websites, if you want them.
IAny info on this, @albertzhao?
IAs an addition to this, since we took a look in DM and it's now sort of working. The root of a domain doesn't work, because it won't get a CNAME back, but an A due to flattening for the DNS spec. If you add or some other subdomain it works correctly (altough the UI is a bit confused). If you then proxy this subdomain (which works) and then try to CNAME to it the issue that Pages runs before most other things (like my Worker) makes it so that the cert is wrong on the "origin".
II hope it makes sense @geelen.
LHello, does anyone know if pages pulls git lfs files? Some images on my site are broken but are returning a 200 status code. I'm trying to work out why this is and I'm wondering if that's the reason.
LThank you. Is this what you need?
unknown.png232.53KB
LIt's img/plug.gif that's not loading
LIt's stored in LFS
LInterestingly, .png files appear to work, whereas .gif files do not. These links are from the same build. Is there a handler for the gif mime type?
https://lukenelson-dev.pages.dev/img/Luke-Nelson-Icon_128x128.png
https://lukenelson-dev.pages.dev/img/background.gif
https://lukenelson-dev.pages.dev/img/Luke-Nelson-Icon_128x128.png
https://lukenelson-dev.pages.dev/img/background.gif
Lunknown.png52.32KB
LAhh, that' the pointer to the LFS file. So it is an LFS issue. Thanks for that 
IThe delete a project is a known bug. WIP...
INo worries, it was a common question ahah
LYou choose it when you create the project.
unknown.png120.1KB
LThere's a rename option in the settings too.
unknown.png84.14KB
Rhey @albertzhao 
how would be the fix look like, would it be a toggle for LFS enabled repo, or will it just automatic?
disclaimer: I don't have access to pages beta yet. But I'm equally curious on how a fix would be implemented since all of our repos uses LFS.
how would be the fix look like, would it be a toggle for LFS enabled repo, or will it just automatic?disclaimer: I don't have access to pages beta yet. But I'm equally curious on how a fix would be implemented since all of our repos uses LFS.
LIn Azure Devops, there's a checkbox for LFS. It would be great to have something similar!
unknown.png127.93KB
Ryup, that's exactly what I'm talking about, I'm leaning towards to an automatic fix though.
I suspect the reason for toggle, was they were using under the hood as oppose to . But as of , should be as fast as .
is actually deprecated and this is the PR that deprecated it.
https://github.com/git-lfs/git-lfs/pull/2526
I suspect the reason for toggle, was they were using under the hood as oppose to . But as of , should be as fast as .
is actually deprecated and this is the PR that deprecated it.
https://github.com/git-lfs/git-lfs/pull/2526
GitHub
This pull request marks the git-lfs(1) 'clone' command as deprecated, and puts that deprecation behind a "feature flag".
Since merging #2511, git clone is as fast ...
Since merging #2511, git clone is as fast ...
Nhey, I was wondering, how long is the line to get into pages?
N@albertzhao dm sent, thanks!
LPlease can you ping me when it's live so I can re-trigger a build. Thank you!
Thank you!