-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Algolia search #15
Comments
@ronaldtse Do you have Algolia API key and index name for Ribose Open hub site? Your sample code above appears to be for Metanorma project site (which is good and works, but I’d like to test the search feature on a hub site too before releasing it as part of OP framework). |
The API key is: 40a5c3929d2f6d51c9a062d2bdf00c20 The index however hasn't been created yet. |
@strogonoff could we get this done soon? Thanks! |
Thanks for the heads-up. I’ll enable this but we’ll see how it works. Not sure whether we can make Algolia index content on project sites that are part of hub site but hosted on separate domains.
… On 8 Jan 2019, at 11:07 AM, Ronald Tse ***@***.***> wrote:
@strogonoff could we get this done soon? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@ronaldtse this is blocked because we need API key and a dedicated index name for each site. (Currently I don’t have Algolia index name for open.ribose.com 🤷♂️) |
Index name: prod_riboseopen |
OK that was quick! |
I get “Invalid Application-ID or API key” when I try searching while running the Jekyll site locally; pushing an update to see how it works in production. Should be live in a few min. Config used:
|
Yep, Algolia error on production site, either index name or API key is incorrect 🤷♂️ @ronaldtse could you check? api_key: '40a5c3929d2f6d51c9a062d2bdf00c20' |
Just pinged you 👍 |
For @strogonoff
The text was updated successfully, but these errors were encountered: