feat: Update Algolia index on master merge #10032
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduce a script to index the static docs HTML files generated by Next.js into Algolia.
It's a migration from the Gatsby solution, which relied on the
gatsby-plugin-algolia
hereThe record generation logic is reused as is, with two notable changes:
Required environment variables before the merge (repo secrets):
ALGOLIA_APP_ID=OOK48W9UCL
ALGOLIA_API_KEY
: The write API keyALGOLIA_INDEX_PREFIX
: (sentry-
), which will show up assentry-docs
(index name) on AlgoliaNEXT_PUBLIC_ALGOLIA_APP_ID=OOK48W9UCL
NEXT_PUBLIC_ALGOLIA_SEARCH_KEY=ca98597f559459c216891b75989832f8
ALGOLIA_INDEX_PREFIX
can be set to a different string until we make sure this works as expected before setting it tosentry-
Closes #9869
Closes #9876
Closes #9778
Closes #6978