Algolia Search Proxy Endpoint

[calebjacob]

Closes: https://pagodaplatform.atlassian.net/browse/DEC-1402

After talking with @pkudinov, we agreed that it made sense to implement a proxy endpoint POST /api/search that can be used by VM components - this will hide the secrets from the frontend. The "App Store" will be the first feature using this endpoint to support searching for apps.

Inside a VM component, you can access the search endpoint:

asyncFetch("/api/search", {
    body: JSON.stringify(body),
    headers: {
      "Content-Type": "application/json",
    },
    method: "POST",
  }).then(...).catch(...);

I've already gone ahead and added the new ENV variables to Vercel for all of our gateway environments. Right now there's only a MAINNET indexer, but we can easily update the beta.near.org ENV variables to use a TESTNET version whenever it's ready.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
near-discovery	✅ Ready (Inspect)	Visit Preview	Aug 16, 2023 5:02pm
near-discovery-testnet	✅ Ready (Inspect)	Visit Preview	Aug 16, 2023 5:02pm

[mpeterdev]

is this necessary? This section of their docs suggests that a search API key is not sensitive and can be included in frontend code

https://www.algolia.com/doc/guides/security/api-keys/#search-only-api-key

[pkudinov]

We would like to use search in multiple different components, including in externally owned components, and given that we are not sure about Algolia long-term, we want to make sure we have an easy way to swap the search. In addition, if we decide to upgrade or rebuild search index, the URL will change, requiring all components (including externally owned) to update