-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
I2I: Deployment and serving of AMP via Cloudflare #36152
Comments
/cc @ampproject/wg-caching |
Oops, fixed the wg slug in the issue description :) |
I can't recall, was this brought to design review? |
Not yet, this is the I2I for that :) |
It would also be great to directly bring this to the @ampproject/tsc |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Can we please make sure not to close this issue? Thanks. |
Your comment is enough to prevent auto-closing this issue :) |
Summary
This I2I discusses the concrete steps and timeline for performing the disentangling of the AMP runtime CDN and the Google AMP Cache.
Implementation guidelines — * * * this is the thing that needs reviewing in this I2I * * *
https://docs.google.com/document/d/1QD0SBwgmZxrvJTpv68ytTI2oKxq4EOi-mkSCKm2JTPc/edit
Design Document
Design document with analysis of alternatives considered, privacy, and security consideration: https://docs.google.com/document/d/1IMfhVgxCRW0Cq1N7xvflfcoxGdnVshvA92je_wDxAY0/edit
Motivation
Alternative Solutions
Launch Tracker
https://docs.google.com/spreadsheets/d/1QL42wafo1jODim8EN5HujEbxw12EeG-trGECnbzDjQA/edit
Notifications
/cc @ampproject/wg-infra @ampproject/wg-performance @ampproject/wg-security-privacy @ampproject/wg-caching @ampproject/wg-foundation-onboarding @ampproject/tsc
The text was updated successfully, but these errors were encountered: