Add Chatbot

[chocolatecupcake2002]

Add Chatbot

Issue Number: #2

closes: #2

Screenshots

Checklist:

• I have mentioned the issue number in my Pull Request.
• I have commented my code, particularly in hard-to-understand areas
• I have gone through the contributing.md file before contributing

Additional context:

1. The chatbot files are kept under the components directory.
2. Limited set of Banned words are listed to prevent unrequired searches by users.
3. For dynamics of vite, the flask file is migrated to a jsx file as rendering templates using jinja engine throws error for front-end server.
4. Queries and Api are under limited set of queries per month under the free-use tier for google custom search.

[vercel]

@chocolatecupcake2002 is attempting to deploy a commit to the pranavbarthwal's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thank you for submitting your pull request! We'll review it as soon as possible. For further communication, you can contact the mentors for this project.

[gitguardian]

⚠️ GitGuardian has uncovered 2 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
-		Google API Key	2919e6a	src/components/Chatbot/backend.js	View secret
-		Google API Key	3d4c328	src/components/Chatbot/backend.js	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.}

[chocolatecupcake2002]

@PranavBarthwal The security check is raised for API.. should I remove the key and custom search engine ID?

Any suggestions will be great! thanks

[PranavBarthwal]

@PranavBarthwal The security check is raised for API.. should I remove the key and custom search engine ID?

Any suggestions will be great! thanks

Add it as an environment variable.
Also add it in the demo .env file

[chocolatecupcake2002]

@PranavBarthwal The security check is raised for API.. should I remove the key and custom search engine ID?
Any suggestions will be great! thanks

Add it as an environment variable. Also add it in the demo .env

i will leave it as DEMO_KEY in demo .env file? for the environment variable

[PranavBarthwal]

@PranavBarthwal The security check is raised for API.. should I remove the key and custom search engine ID?
Any suggestions will be great! thanks

Add it as an environment variable. Also add it in the demo .env

i will leave it as DEMO_KEY in demo .env file? for the environment variable

Yeaah, just name it properly like CHATBOT_API_KEY & CUSTOM_SEARCH_ENGINE_ID

[chocolatecupcake2002]

@PranavBarthwal
I have changed the values in files, yet same issue is present.. is it cached or i try a commit after sometime?

[chocolatecupcake2002]

@PranavBarthwal I have changed the values in files, yet same issue is present.. is it cached or i try a commit after sometime?

@PranavBarthwal

[chocolatecupcake2002]

@PranavBarthwal

[chocolatecupcake2002]

@PranavBarthwal

@PranavBarthwal

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
cosmo-xplore	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 7, 2024 8:22am

[PranavBarthwal]

Chatbot is good but please restore the original background gradient.

[chocolatecupcake2002]

Chatbot is good but please restore the original background gradient.

Great to know, can you clarify on original background gradient? you would like the previous css i had placed (black..white.. shown in issues) or the same as of webpage?

[PranavBarthwal]

Chatbot is good but please restore the original background gradient.

Great to know, can you clarify on original background gradient? you would like the previous css i had placed (black..white.. shown in issues) or the same as of webpage?

nvm, someone had submitted the PR for that, so its fixed now. Just resolve the conflicts and tag me once its done, and it'll be merged.

[chocolatecupcake2002]

@PranavBarthwal the conflict is resolved pls check

[chocolatecupcake2002]

@PranavBarthwal can i know when the score will be added for closing this issue and how much is allocated for this task? also requesting to add in contributors list :) thanks.

[PranavBarthwal]

@PranavBarthwal can i know when the score will be added for closing this issue and how much is allocated for this task? also requesting to add in contributors list :) thanks.

Next time the leaderboard is updated, you'll be able to see your score in the leaderboard. You'll get 40 or 45 points as this was level 3 issue.
Contributors list will get updated automatically after some time