The Orama logo is returning a 404

[bjohansebas]

Just so you know, the logo is returning a 404. There isn’t a new URL to fetch it from, and I’ve already contacted Orama to find out where we can get the logo.

[gurgunday]

FYI, search doesn't work for me either, and we have the same issue over at Fastify: fastify/website#420

---

[ovflowd]

What are the network requests giving? Any errors?

I guess we gotta move to the locally generated orama database?

[araujogui]

What are the network requests giving? Any errors?

I guess we gotta move to the locally generated orama database?

{"error":"Cannot facet by \"[\"siteSection\"]\": no index has that field"}

[bmuenzenmeyer]

Search is working for me right now, but not AI summary - though i see responses in the console, just not rendering

[araujogui]

Search is working for me right now, but not AI summary - though i see responses in the console, just not rendering

Weird, not working here yet, maybe your request responses are cached?

[mikeesto]

I cleared my browser cache, and tried a few different browsers, and search is working for me too. The logo is 404

[AugustinMauroy]

cc @micheleriva

[micheleriva]

@AugustinMauroy sadly I am not involved with Orama anymore. You should send a support request to support@orama.com

[bjohansebas]

For the logo, it's here: https://drive.google.com/drive/folders/1J8gnbRHBFa3bf2A7h-hWlP_9hWgNJvox?usp=sharing. I have an open PR, but I won’t be able to finish it until the weekend, so go ahead if anyone wants to take it.

Regarding the search not working—have you tried rotating the tokens? If so, let me know if I should contact Orama; I have a direct contact there.

[ovflowd]

To prevent more spams here, I already shared and highlighted on Slack what our plan should be here, for the website we should be transitioning to the same local orama approach as we've been using on doc-kit for the time being.

This means:

• Remove our current Orama Cloud CI steps and the script
  • Including removing from docs, and what not and all references
• Switch all the code on the website to use the same local-based approach we use on doc-kit
  • The database file should be .gitignored
  • The database file should go to Next.js's asset folder
  • The database file should be generated via a command such as "orama:gen"
  • The database generate command should be added on vercel.json as part of the build steps
• This means that we don't require an Orama DB for the website to function, if none exists, it will just 404 and the UI should simply render no results.
• Generating the file is optional.
• This actually ensures that the Orama DB is consistent with your current version of the codebase. No more Cloud uploads.
• We should eventually disable our Orama Cloud account and not rely on it anymore
• On the long-long-term if we see that the package is abandoned and starting to accumulate security advisories we should switch to an alternative, if any available.

cc @nodejs/nodejs-website @nodejs/web-infra we should create proper tasks and add this to our web-agenda.