Fix backend setup

[Thevishal-kumar]

Description:
I encountered several blocking issues while setting up the project locally on Windows, preventing the application from starting and fetching data.

This PR fixes the database initialization (missing tables), resolves the frontend-backend connection issue (IPv6 vs IPv4 conflict), and corrects a typo in the main navigation UI.

Changes Made
Database: Added the missing CREATE TABLE statement for trending_niches to the initialization script, resolving 500 Internal Server Errors.

Database: Added TRUNCATE cleanup to the seed script to prevent "Duplicate Key" errors when re-running setup.

Frontend Config: Updated vite.config.ts proxy target from localhost to 127.0.0.1 to fix connection refused errors on Windows.

UI: The navigation bar now displays the correct placeholder text.

🤝 Collaboration
Collaborated with: (None)

✅ Checklist
[x] I have read the contributing guidelines.

[x] I have added tests that prove my fix is effective or that my feature works. (Verified locally by successfully running the full stack).

[ ] I have added necessary documentation (if applicable).

[ ] Any dependent changes have been merged and published in downstream modules.

Summary by CodeRabbit

• Chores
  • Updated development server configuration for improved compatibility.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Modified Vite dev server proxy configuration in the frontend build setup, changing the API route proxy target from localhost to 127.0.0.1. No functional behavior changes; purely a host address string update.

Changes

Cohort / File(s)	Summary
Dev Server Configuration Frontend/vite.config.ts	Updated /api proxy target from localhost to 127.0.0.1 for the Vite dev server

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• ishaanxgupta
• Saahi30

Poem

🐰 A hop and a bound through the config domain,
From localhost shores to 127's lane,
The proxy now points with precision so bright,
A tiny tweak ensuring connections align right! 🌟

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The PR title 'Fix backend setup' is overly vague and generic. While the PR includes backend changes (database initialization), the title does not specifically convey what backend issue is being addressed.	Consider a more specific title that indicates the nature of the fixes, such as 'Fix Windows backend setup and database initialization issues' or 'Resolve Windows setup issues with vite proxy and database tables'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

Frontend/vite.config.ts (1)

16-16: Fix is sound; consider making it configurable for multi-environment support.

The change from localhost to 127.0.0.1 correctly resolves the Windows IPv6/IPv4 binding issue. However, hardcoding the address reduces flexibility for developers on different environments or with non-standard backend setups.

Consider reading the proxy target from an environment variable for greater flexibility:

🔎 Proposed enhancement to support environment-driven configuration

 server: {
   proxy: {
-    '/api': 'http://127.0.0.1:8000',
+    '/api': process.env.VITE_API_URL || 'http://127.0.0.1:8000',
   },
 },

With a .env.development or .env file:

VITE_API_URL=http://127.0.0.1:8000

This allows developers to override the address when needed (e.g., for containerized setups or different backend hosts) while defaulting to the Windows-compatible address.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a3be437 and 3a4021b.

📒 Files selected for processing (1)

• Frontend/vite.config.ts