I2I: AMP Runtime Self-Hosting

[sebastianbenz]

Summary

Make it possible for publishers to self-host the AMP runtime, without breaking AMP validity.

Design document

• Design Document
• Design Review presentation

Motivation

The benefits are:

• Independence: AMP runtime and components no longer needs to be loaded from Google servers for AMP First sites.
• Control: AMP First sites can align the roll-out of a new AMP version with their own QA (this won’t help them if pages are served in SERPs). They can also rollback a broken runtime version themselves.
• Performance: faster page load and TTI by avoiding an additional HTTPs connection.

Launch tracker

• Launch Tracker (TBD)

/cc @ampproject/wg-approvers @mattwomple @honeybadgerdontcare

[westonruter]

And then this would also need to be supported in the RewriteAmpUrls optimizer transformer. Namely, there would need to be a way to prevent the ampRuntimeVersion from being appended to the path in calculateHost(), and then the _replaceUrl() transformer method would need to take a rtv argument to conditionally add the query param if configured to do so.

How would that configuration be supplied? In addition to the ampUrlPrefix should there be a boolean like rtvAsQueryParam that defaults to false?

[jridgewell]

How would that configuration be supplied? In addition to the ampUrlPrefix should there be a boolean like rtvAsQueryParam that defaults to false?

I'm not sure we need both params. Presence of ampUrlPrefix could imply query params.

[twifkak]

Hi, haven't been following closely, but just wanted to include https://github.com/ampproject/amppackager/blob/releases/transformer/transformers/urlrewrite.go in the list of things that might need changing.

[samuelspagl]

Hey there,

as this issue is still open since 2021, I wanted to ask what the current status of this is. I would love to self host part of the AMP runtime for the "Google Webstories" Wordpress plugin.

Thanks a lot in advance!