The site is a static site, but today it's still being hosted on a server we own.
The last time there was an outage it was because a deploy wasn't atomically updated. Let's look at how you could debug that.
- You need to have access to the "TypeScript - Public Facing Services" subscription in Azure
We're currently running on App Service, the places where you can find info:
-
Look at the deploy logs.
-
We have 7 day retention of server logs. Generally speaking, they probably aren't useful and would probably get hammered to the 35MB per day pretty quickly anyway.
The build to deploy train normally looks like this:
v2branch gets pushed:- A deploy is made to azure blob storage via
.github/workflows/v2-merged-staging.yml - Every Monday, a deploy is made from v2 to the production app via
.github/workflows/deploy-prod.yml
You can deploy v2 to production anytime via the "Run workflow" button here, so if you have an emergency commit - it goes to v2 then you can run the action.
App Service apps are configured by Web.config. Here's a reference on the format. I've seen files (*.json & *.manifest) be 404s on the site because they were not in the config.
Check the build logs, they are always in GitHub Actions