3pp-mirror/docusaurus
1
0
Fork 0
mirror of https://github.com/facebook/docusaurus.git synced 2025-04-29 02:08:36 +02:00
Code Issues Projects Releases Packages Wiki Activity

docs: Docsearch blog post v1 fixes (#5916)

Browse source
This commit is contained in:
Sébastien Lorber 2021-11-10 11:11:34 +01:00 • committed by GitHub
parent b873486c87
commit dee6c4648e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
website-1.x/blog/2021-11-05-algolia-migration.md
View file

@ -11,11 +11,13 @@ image: /img/blog/2021-05-12-announcing-docusaurus-two-beta/social-card.png
Algolia DocSearch is migrating to a new system.
Docusaurus v1 sites should upgrade too or search will stop working.
Docusaurus v1 sites should upgrade their configuration.
<!--truncate-->
From now on, it is required to use an `appId` in your Docusaurus v1 site configuration:
Algolia will stop crawling and updating your existing index soon, potentially leading to stale search results.
From now on, it will be required to use an `appId` in your Docusaurus v1 site configuration:
```js
const siteConfig = {
@ -28,8 +30,6 @@ const siteConfig = {
module.exports = siteConfig;
```
You should have received an `appId` + `apiKey` by email with an invitation to join the Algolia SaaS application.
The migration will roll out in batches, and you should receive a new `appId` and `apiKey` by email soon, with an invitation to join the Algolia SaaS application.
If you didn't receive any email, please reach out to the Algolia DocSearch support team and they'll invite you.
Further information will be provided on the Docusaurus v2 blog.
More information can be found in on the [DocSearch migration page](https://docsearch.algolia.com/docs/migrating-from-legacy) and we will publish a [Docusaurus v2 blog post](https://v2.docusaurus.io/blog).