Skip to content
This repository has been archived by the owner on Mar 14, 2024. It is now read-only.

Deploying the site

Jump to bottom
Ewa edited this page Oct 13, 2022 · 3 revisions

developer.chrome.com is hosted on App Engine under the chrome-apps-doc project. (You can access the deployed site directly if you want.)

The choice of App Engine is largely dictated by internal Google requirements: the subdirectories /devsummit/ and /origintrials/ are routed to different App Engine projects, configured in a way that is unique to Google internal Cloud projcts.

Even though developer.chrome.com uses App Engine and not Firebase Hosting, much of the way we build using Cloud Build is the same as on web.dev.

This includes the automated fashion in which builds are undertaken. You can deploy builds manually, but unless you disable the tasks set up in Cloud Scheduler (which eventually trigger Cloud Builds), then your work will get overwritten every hour or so.

Algolia works roughly the same way, generating "dist/algolia.json" which is read and indexed as part of the build.

Excluding files from a deploy - .gcloudignore

We use .gcloudignore file to make the number of files included in a deploy as small as possible.

Files that need to be always included in the deploy are:

  • /dist => the static site
  • /server => GAE server
  • modules and configs needed to render an 11ty page on demand (used in the /render handler):
    • /site, apart from static .md, .html files and images
    • .eleventy
    • /external/data
Clone this wiki locally