search

google / gvisor-website

The gVisor project website.
https://gvisor.dev/
Apache License 2.0
17 stars 19 forks source link

Use of Content Delivery Network #130

Open realabbas opened 4 years ago

realabbas commented 4 years ago

Use of Content Delivery Network to serve static components

There are 9 static components that are not on CDN.

https://gvisor.dev/scss/main.min.a6b803b675e6be3fa855ba1c5de7a6a3c6e0aa5a48b97fa1c41128e8e9b7cb8d.css
https://gvisor.dev/background_hu7001f5438b9e69fd36c11bbcd7ce28bc_1070364_1920x1080_fill_q75_catmullrom_top.jpg
https://gvisor.dev/js/jquery-3.3.1.min.js
https://gvisor.dev/js/d3.v4.min.js
https://gvisor.dev/logo_huecc535c5c6d57d0972f257cbe0c4e09e_8387_70x70_fit_catmullrom_2.png
https://gvisor.dev/img/powered-gvisor.png
https://gvisor.dev/js/popper.min.js
https://gvisor.dev/js/bootstrap.min.js
https://gvisor.dev/js/main.min.bdc747859423a89c29f21e41c5dfda2cefbfe771ea5fe61e56871467c5473856.js

The static components should be hosted on CDN and served from there.

ianlewis commented 4 years ago

@realabbas This was sort of discussed a bit in #96. We have a requirement to serve the content from the same domain. We could serve content via CDN if we used static_files/static_dir in the app.yaml but it would make app.yaml more complex and hasn't been a high priority so far.

Are you seeing poor performance on the website?