Veronika algolia plugin

[VPilipenko334]

This is an Algolia Search Integration to add to the unified-demo. This way, if customers are planning on using Algolia, we can demo how it integrates with Builder, as well as be able to show them how it works in the Visual Editor UI.

Here is a loom video walkthrough of me using it.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
unified-demo-ecomm	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 1, 2024 8:48pm

[gitguardian]

⚠️ GitGuardian has uncovered 5 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
14353166	Triggered	Algolia Keys	8fe3797	ecommerce/.env	View secret
13657484	Triggered	Generic High Entropy Secret	4050b82	ecommerce/.env	View secret
13088346	Triggered	Generic High Entropy Secret	4050b82	ecommerce/.env	View secret
13360254	Triggered	Generic High Entropy Secret	4050b82	ecommerce/.env	View secret
13088346	Triggered	Generic High Entropy Secret	4050b82	ecommerce/.env	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[VPilipenko334]

maybe kind of a silly question but do you know why GitGuardian is saying that the API keys are exposed? I was under the impression that . meant it would omit that file from being uploaded/shown