Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use a CDN? #61

Closed
Rich-Harris opened this issue Mar 19, 2017 · 3 comments
Closed

Use a CDN? #61

Rich-Harris opened this issue Mar 19, 2017 · 3 comments

Comments

@Rich-Harris
Copy link
Member

See https://www.webpagetest.org/result/170319_60_SFP/2/performance_optimization/#use_of_cdn

@maxmilton
Copy link

Looking at the headers on the site now it looks like it's already using Cloudflare so this could probably be closed. FYI, if it's not already, you should submit the site for open source sponsorship:
https://blog.cloudflare.com/cloudflare-open-source-your-upgrade-is-on-the-house/

Now that the CDN is all good, the next step for performance might be to fix the crazy site file size. I've created a seperate issue for that: #345

@Conduitry
Copy link
Member

The website is currently using a Let's Encrypt certificate, which is making me think that Rich isn't using Cloudflare directly. (The last time I used Cloudflare's free universal SSL, it was some Comodo cert valid for a bunch of different domains.) So I'm guessing this is Cloudflare being leveraged internally by Now.sh or something.

But also: I'm not too sure how well Svelte could be considered "volunteer-run or working on a non-profit basis" (which is a requirement for Cloudflare's "free pro account for OSS" offer). A lot of the work on Svelte occurs while Rich is on the clock at the New York Times.

Of course, it's always possible that the website is indeed on a pro Cloudflare plan, and that's why it's able to have a custom certificate.

Anyway, tl;dr ... I'm actually not sure what the tl;dr is.

@Rich-Harris
Copy link
Member Author

So I'm guessing this is Cloudflare being leveraged internally by Now.sh or something.

Exactly that — Now does this for all new deployments. I guess we can close this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants