Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 13 additions & 9 deletions Backend/.env-example
Original file line number Diff line number Diff line change
@@ -1,10 +1,14 @@
user=postgres
password=[YOUR-PASSWORD]
host=
port=5432
SUPABASE_URL=[URL]
SUPABASE_KEY=[YOUR-SUPABASE-KEY]

user=postgres.<project>
password=[YOUR-PASSWORD]
host=aws-<location>.pooler.supabase.com
port=5432
dbname=postgres
GROQ_API_KEY=
SUPABASE_URL=
SUPABASE_KEY=
GEMINI_API_KEY=
YOUTUBE_API_KEY=

GROQ_API_KEY=[YOUR-GROQ-API-KEY]

GEMINI_API_KEY=[YOUR-GEMINI-API-KEY]

YOUTUBE_API_KEY=[YOUR-YOUTUBE-API-KEY]
89 changes: 77 additions & 12 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,15 +84,15 @@ Ensure you have the following installed:
#### 1. Clone the repository

```sh
git clone https://github.com/AOSSIE-Org/InPact.git
cd inpact
git clone https://github.com/AOSSIE-Org/InPactAI.git
cd InPactAI
```

#### 2. Frontend Setup

1. Navigate to the frontend directory:
```sh
cd frontend
cd Frontend
```

2. Install dependencies:
Expand All @@ -116,23 +116,34 @@ npm install

1. Navigate to the backend directory:
```sh
cd ../backend
cd Backend
```

2. Install dependencies:
2. Create a virtual environment
```sh
pip install -r requirements.txt
python -m venv venv
```

3. Activate the virtual environment
```sh
venv\Scripts\activate
```
Comment on lines +127 to +130
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟑 Minor

Add cross-platform venv activation instructions.

The activation command is Windows-specific. Issue #178 explicitly requested instructions for Windows/macOS/Linux.

πŸ“ Suggested fix
 3. Activate the virtual environment
+
+   **Windows:**
 ```sh
 venv\Scripts\activate
  • macOS/Linux:
    +sh +source venv/bin/activate +
</details>

<!-- suggestion_start -->

<details>
<summary>πŸ“ Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion
3. Activate the virtual environment

   **Windows:**
πŸ€– Prompt for AI Agents
In @README.md around lines 127 - 130, The README currently shows only the
Windows-specific virtual environment activation command (venv\Scripts\activate);
update the venv activation section to include cross-platform instructions by
keeping the existing Windows command and adding macOS/Linux activation using
source venv/bin/activate (and optionally the PowerShell/Mac zsh variants if
desired) so users on Windows, macOS, and Linux can follow the correct command.


3. Navigate to the app directory:
4. Install dependencies:
```sh
pip install -r requirements.txt
```

5. Navigate to the app directory:
```sh
cd app
```

4. Create a `.env` file using `.env-example` as a reference.
6. Create a `.env` file

- Use `.env-example` file as reference

5. Obtain Supabase credentials:
7. Obtain Supabase credentials:

- Go to [Supabase](https://supabase.com/)
- Log in and create a new project
Expand Down Expand Up @@ -161,10 +172,64 @@ cd app
```


6. Get the Groq API key:
8. Get the Groq API key:
- Visit [Groq Console](https://console.groq.com/)
- Create an API key and paste it into the `.env` file

9. Get the YouTube API key:
- Visit [Groq Console](https://console.cloud.google.com/)
Comment on lines +179 to +180
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟑 Minor

Fix incorrect link text.

Line 180 says "Visit [Groq Console]" but links to Google Cloud Console. This appears to be a copy-paste error from step 8.

πŸ“ Suggested fix
 9. Get the YouTube API key:
-   - Visit [Groq Console](https://console.cloud.google.com/)
+   - Visit [Google Cloud Console](https://console.cloud.google.com/)
πŸ“ Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
9. Get the YouTube API key:
- Visit [Groq Console](https://console.cloud.google.com/)
9. Get the YouTube API key:
- Visit [Google Cloud Console](https://console.cloud.google.com/)
πŸ€– Prompt for AI Agents
In @README.md around lines 179 - 180, Replace the incorrect link text "Visit
[Groq Console]" in step 9 with the correct label "Visit Google Cloud Console"
(or change the bracketed text to "[Google Cloud Console]") so the link target
(https://console.cloud.google.com/) matches its visible text; ensure the change
is applied to the step that begins "Get the YouTube API key:" so it is
consistent with step 8.

- Sign in with your Google Account
- Select "Default Project" or Create "New Project", Look at the top
- In sidebar go to "APIs & Services" then click "Library"
- Serach "YouTube Data API v3"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟑 Minor

Typo: "Serach" β†’ "Search".

πŸ“ Suggested fix
-   - Serach "YouTube Data API v3"
+   - Search "YouTube Data API v3"
πŸ“ Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- Serach "YouTube Data API v3"
- Search "YouTube Data API v3"
πŸ€– Prompt for AI Agents
In @README.md at line 184, Fix the typo "Serach" in the README at the occurrence
that reads 'Serach "YouTube Data API v3"' by replacing it with "Search" so the
line reads 'Search "YouTube Data API v3"'; update the README.md accordingly.

- Click Enable
- Now again go to "APIs & Services" then click "Credentials"
- Click "Create Credentials" then "API key"
- Click "Show Key" and copy the API key and paste it into the `.env` file

10. Get the Gemini API key:
- Visit [Google AI Studio](https://aistudio.google.com/)
- SignIn/SignUp with Google account
- Click "API Keys" left side panel
- Click "Create API Key"
- Name your key "..." and select "Default Gemini Project"
- Click "Create key"
- Paste the API Key into the `.env` file

11. Final `.env` file should look:

```sh
SUPABASE_URL=[URL]
SUPABASE_KEY=[URL]

user=postgres
password=[YOUR-PASSWORD]
host=db.wveftanaurduixkyijhf.supabase.co
port=5432
dbname=postgres

GROQ_API_KEY=[URL]

GEMINI_API_KEY=[URL]
```

[The above works in ipv6 networks, if you are in ipv4 network or it cause errors, use the below connection string which could be found in Session Pooler connection]

```sh
SUPABASE_URL=[URL]
SUPABASE_KEY=[URL]

user=postgres.<project>
password=[YOUR-PASSWORD]
host=aws-<location>.pooler.supabase.com
port=5432
dbname=postgres

GROQ_API_KEY=[URL]

GEMINI_API_KEY=[URL]
```
Comment on lines +199 to +231
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟑 Minor

Final .env examples are missing YOUTUBE_API_KEY.

Step 9 documents obtaining the YouTube API key, and Backend/.env-example includes YOUTUBE_API_KEY, but both final .env examples here omit it. Additionally, consider using more descriptive placeholders like [YOUR-GROQ-API-KEY] instead of [URL] for API keys (consistent with .env-example).

πŸ“ Suggested fix (showing IPv6 block; apply same to IPv4 block)
    ```sh
    SUPABASE_URL=[URL]
-   SUPABASE_KEY=[URL]
+   SUPABASE_KEY=[YOUR-SUPABASE-KEY]

    user=postgres
    password=[YOUR-PASSWORD]
    host=db.wveftanaurduixkyijhf.supabase.co
    port=5432
    dbname=postgres

-   GROQ_API_KEY=[URL]
+   GROQ_API_KEY=[YOUR-GROQ-API-KEY]

-   GEMINI_API_KEY=[URL]
+   GEMINI_API_KEY=[YOUR-GEMINI-API-KEY]
+
+   YOUTUBE_API_KEY=[YOUR-YOUTUBE-API-KEY]
    ```
πŸ€– Prompt for AI Agents
In @README.md around lines 199 - 231, The final .env examples in README.md are
missing YOUTUBE_API_KEY and use vague [URL] placeholders; update both IPv6 and
IPv4 example blocks to include a YOUTUBE_API_KEY entry (e.g.,
YOUTUBE_API_KEY=[YOUR-YOUTUBE-API-KEY]) and replace SUPABASE_KEY, GROQ_API_KEY,
and GEMINI_API_KEY placeholders with descriptive tokens like
[YOUR-SUPABASE-KEY], [YOUR-GROQ-API-KEY], [YOUR-GEMINI-API-KEY] to match
Backend/.env-example and make the intent clear.


#### 4. Start Development Servers


Expand All @@ -173,9 +238,9 @@ cd app
npm run dev
```

2. Start the backend server (from the backend/app directory):
2. Start the backend server (from the backend directory):
```sh
uvicorn main:app --reload
uvicorn app.main:app --reload
```

## Data Population
Expand Down