Emergency Runbook
This site is hosted on Gatsby Cloud. It is maintained and supported by New Relic's Docs Engineering team. If you have any questions or comments, please reach out to docs-engineering@newrelic.com.
To diagnose a particular alert, we've started a Common Issues
Use the Gatsby Cloud UI to select a previous build and redeploy that build.
First, determine the desired previous build:
- Navigate to the Releases tab in the opensource-website repo.
- Determine which release to rollback to. Typically, this should be
latest_release - 1. However, you might need to go back further. Click the commit hash (in this case,12f5187).
- Use this commit message/hash value to locate the corresponding build in the Gatsby Cloud UI.
Steps to redeploy in Gatsby Cloud:
- Log into Gatsby Cloud using your GitHub login.
- Select the
opensource-websitesite, main branch.
- Click the
View production historybutton to see all the previous builds that have run. - Find the appropriate build corresponding to the release you located from the repo releases. This is the build to roll back to. Click
Publishto select that build for deployment.
- That should produce a pop up. Uncheck
Disable automatic deploysand clickPublish.
- Notify the hero in #help-deven-websites of the rollback so we can address the underlying issue.
This project supports three environments, local development, staging (a.ka. development), and production.
Note: When building the site, Gatsby coerces anything you've set in NODE_ENV to production
Corresponds to the main branch
New Relic Domains: https://opensource.newrelic.com
Corresponds to the develop branch
Gatsby Cloud Domain: https://opensourcewebsitedevelop.gatsbyjs.io/ New Relic Domains:
To run, execute yarn start from the root of this repository.
Should you want Tessen instrumentation while developing locally, you will need to add an additional configuration option to gatsby-config.js for the gatsby-plugin-newrelic plugin.
The site is a combination of template-generated pages and single pages built using React, markup, and MDX.
Beyond the CI/CD automation, GitHub Actions are used to keep the stats data related to each project updated on a scheduled basis. Some of the architecture consequences of that change are described here.
No issues yet!