A Vite-powered React site for Rishabh Agrawal's portfolio, featuring a Gemini chatbot (powered by gemini-2.5-flash) and roast mode.
For local development, create a .env or .env.local file in the project root with the following values:
VITE_GEMINI_API_KEY=<your_google_generative_ai_key>
VITE_FIREBASE_API_KEY=<your_firebase_api_key>
VITE_FIREBASE_AUTH_DOMAIN=<your_firebase_auth_domain>
VITE_FIREBASE_PROJECT_ID=<your_firebase_project_id>
VITE_FIREBASE_STORAGE_BUCKET=<your_firebase_storage_bucket>
VITE_FIREBASE_MESSAGING_SENDER_ID=<your_firebase_messaging_sender_id>
VITE_FIREBASE_APP_ID=<your_firebase_app_id>
You can copy .env.example to .env and update the values as needed.
Then run the dev server as usual:
npm install
npm run dev
The deployment workflow expects the following repository secrets to be configured:
GEMINI_API_KEY- Maps toVITE_GEMINI_API_KEYfor the Gemini chatbot (use an HTTP referrer–restricted key scoped tohttps://saint2706.github.ioso it doesn't get flagged as leaked)FIREBASE_API_KEY- Maps toVITE_FIREBASE_API_KEYFIREBASE_AUTH_DOMAIN- Maps toVITE_FIREBASE_AUTH_DOMAINFIREBASE_PROJECT_ID- Maps toVITE_FIREBASE_PROJECT_IDFIREBASE_STORAGE_BUCKET- Maps toVITE_FIREBASE_STORAGE_BUCKETFIREBASE_MESSAGING_SENDER_ID- Maps toVITE_FIREBASE_MESSAGING_SENDER_IDFIREBASE_APP_ID- Maps toVITE_FIREBASE_APP_ID
Ensure these secrets are configured in the repository settings for the application to work correctly in production.