Security Issue: .env file committed

[sherukoda]

Hi Sampad Gorai,

I saw that the .env file was committed in the project. Since it contains sensitive keys, it should not be in the repo. Please do the following:

1. Delete the current repo (or make it private right away).

2. On your local machine:

   • Remove the .env file.

   • Add .env to .gitignore.

   • Create a .env.example file with placeholders, for example:

     VITE_SUPABASE_URL=your-url-here
     VITE_SUPABASE_ANON_KEY=your-anon-key-here
     

3. Push the project again to a fresh repo without the .env file.

4. Regenerate/rotate all the exposed keys (Supabase, APIs, etc.) because they are already public.

This will keep the project safe and professional.