Fix/qdrant auth upload

.cursor/rules/general-rule.mdc

@@ -1,11 +1,15 @@
 ---
-description: 
-globs: 
+description:
+globs:
 alwaysApply: true
 ---
+
 ## Rules to Follow
 
-- You must always commit your changes whenever you update code. 
+- You always prefer to use branch development.
+- Before writing any code, you create a feature branch to hold those changes.
+- After you are done, provide instructions in a "Merge.md" file that explains how to merge the changes back to main with both a Github PR route and a Github CLI route.
+- You must always commit your changes whenever you update code.
 - You must always try and write code that is well documented. (self or commented is fine)
 - You must only work on a single feature at a time.
-- You must explain your decisions thouroughly to the user.
+- You must explain your decisions thouroughly to the user.

Merge.md

@@ -0,0 +1,166 @@
+# Merge Instructions
+
+This repo follows a branch-based workflow. Current work for the Qdrant auth fix is on `fix/qdrant-auth-upload`. Previous UI work was done on `fix/chat-question-overwrite`.
+Previous rollback context remains available on `rollback/ca7e9c0` (reset to commit `ca7e9c03403e3053ede6a2d14b00531facf95d98`).
+
+## Create PR on GitHub (UI Route)
+
+1. Push your branch (if not already pushed):
+
+```bash
+git push -u origin fix/qdrant-auth-upload
+```
+
+2. Open a Pull Request from `fix/qdrant-auth-upload` into `main` on GitHub.
+3. Add reviewers and wait for approvals and CI to pass.
+4. Use “Squash and merge” or your preferred merge strategy.
+
+## GitHub CLI Route
+
+From the repo root:
+
+```bash
+git push -u origin fix/qdrant-auth-upload
+gh pr create --fill --base main --head fix/qdrant-auth-upload
+gh pr view --web   # optional, open in browser
+gh pr merge --merge   # or --squash / --rebase per your preference
+```
+
+## Post-merge cleanup
+
+```bash
+git checkout main
+git pull origin main
+git branch -d fix/qdrant-auth-upload
+```
+
+## Notes for Reviewers
+
+- Rollback branch `rollback/ca7e9c0` points to commit `ca7e9c0`.
+- Effectively reverts subsequent changes after `ca7e9c0` by merging this branch.
+- Validate that critical functionality at that commit still builds/tests cleanly.
+- Any newer work has been preserved on its original feature branches.
+
+# Deployment Instructions
+
+This project consists of two separate deployments:
+
+1. Frontend (Next.js)
+2. API (FastAPI)
+
+## API Deployment
+
+### Prerequisites
+
+1. Install Vercel CLI:
+
+```bash
+npm install -g vercel
+```
+
+2. Login to Vercel:
+
+```bash
+vercel login
+```
+
+### Deploy API
+
+1. Navigate to the API directory:
+
+```bash
+cd api
+```
+
+2. Deploy to Vercel:
+
+```bash
+vercel
+```
+
+3. After deployment, copy the API URL (you'll need it for the frontend)
+
+### Environment Variables for API
+
+Set these in your Vercel project dashboard:
+
+- `OPENAI_API_KEY`: Your OpenAI API key
+
+## Frontend Deployment
+
+### Prerequisites
+
+Same as API deployment (Vercel CLI and login)
+
+### Deploy Frontend
+
+1. Navigate to the frontend directory:
+
+```bash
+cd frontend
+```
+
+2. Deploy to Vercel:
+
+```bash
+vercel
+```
+
+### Environment Variables for Frontend
+
+Set these in your Vercel project dashboard:
+
+- `NEXT_PUBLIC_API_URL`: The URL of your deployed API (e.g., https://your-api.vercel.app)
+
+## Monitoring and Management
+
+### API Project
+
+1. Monitor API logs and performance in Vercel dashboard
+2. Check Function execution logs
+3. Monitor API rate limits and usage
+
+### Frontend Project
+
+1. Monitor build logs and deployment status
+2. Check static asset delivery
+3. Monitor page performance
+
+## Troubleshooting
+
+### API Issues
+
+1. Check API logs in Vercel dashboard
+2. Verify environment variables are set
+3. Test API endpoints directly
+
+### Frontend Issues
+
+1. Check build logs
+2. Verify API URL is correctly set
+3. Check browser console for errors
+4. Verify API is accessible from frontend domain
+
+## Alternative: GitHub PR Route
+
+1. For API changes:
+
+```bash
+cd api
+gh pr create --title "Deploy API changes" --body "Deploy latest API changes to Vercel"
+```
+
+2. For Frontend changes:
+
+```bash
+cd frontend
+gh pr create --title "Deploy Frontend changes" --body "Deploy latest Frontend changes to Vercel"
+```
+
+3. After PRs are merged:
+
+```bash
+gh pr merge
+```
+
+Vercel will automatically deploy changes when merged to main branch for each project.

README.md

@@ -3,7 +3,6 @@
      height="auto"/>
 </p>
 
-
 ## <h1 align="center" id="heading"> 👋 Welcome to the AI Engineer Challenge</h1>
 
 ## 🤖 Your First Vibe Coding LLM Application
@@ -27,7 +26,6 @@ That's it! Head to the next step and start building your application!
 
 </details>
 
-
 <details>
   <summary>🏗️ Forking & Cloning This Repository</summary>
 
@@ -43,81 +41,96 @@ Got everything in place? Let's move on!
 
 1. Fork [this](https://github.com/AI-Maker-Space/The-AI-Engineer-Challenge) repo!
 
-     ![image](https://i.imgur.com/bhjySNh.png)
+   ![image](https://i.imgur.com/bhjySNh.png)
 
 1. Clone your newly created repo.
 
-     ``` bash
-     # First, navigate to where you want the project folder to be created
-     cd PATH_TO_DESIRED_PARENT_DIRECTORY
+   ```bash
+   # First, navigate to where you want the project folder to be created
+   cd PATH_TO_DESIRED_PARENT_DIRECTORY
+
+   # Then clone (this will create a new folder called The-AI-Engineer-Challenge)
+   git clone [email protected]:<YOUR GITHUB USERNAME>/The-AI-Engineer-Challenge.git
+   ```
+
+   > Note: This command uses SSH. If you haven't set up SSH with GitHub, the command will fail. In that case, use HTTPS by replacing `[email protected]:` with `https://github.com/` - you'll then be prompted for your GitHub username and personal access token.
 
-     # Then clone (this will create a new folder called The-AI-Engineer-Challenge)
-     git clone [email protected]:<YOUR GITHUB USERNAME>/The-AI-Engineer-Challenge.git
-     ```
+1. Verify your git setup:
 
-     > Note: This command uses SSH. If you haven't set up SSH with GitHub, the command will fail. In that case, use HTTPS by replacing `[email protected]:` with `https://github.com/` - you'll then be prompted for your GitHub username and personal access token.
+   ```bash
+   # Check that your remote is set up correctly
+   git remote -v
 
-2. Verify your git setup:
+   # Check the status of your repository
+   git status
 
-     ```bash
-     # Check that your remote is set up correctly
-     git remote -v
+   # See which branch you're on
+   git branch
+   ```
 
-     # Check the status of your repository
-     git status
+    <!-- > Need more help with git? Check out our [Detailed Git Setup Guide](docs/GIT_SETUP.md) for a comprehensive walkthrough of git configuration and best practices. -->
 
-     # See which branch you're on
-     git branch
-     ```
+1. Open the freshly cloned repository inside Cursor!
 
-     <!-- > Need more help with git? Check out our [Detailed Git Setup Guide](docs/GIT_SETUP.md) for a comprehensive walkthrough of git configuration and best practices. -->
+   ```bash
+   cd The-AI-Engineering-Challenge
+   cursor .
+   ```
 
-3. Open the freshly cloned repository inside Cursor!
+1. Check out the existing backend code found in `/api/app.py`
 
-     ```bash
-     cd The-AI-Engineering-Challenge
-     cursor .
-     ```
+### Root Python Environment with `uv`
 
-4. Check out the existing backend code found in `/api/app.py`
+To keep things tidy, we use a single root-level virtual environment and install all Python deps at the repo root using `uv`.
+
+```bash
+# At repo root
+uv venv .venv
+source .venv/bin/activate   # Windows: .venv\Scripts\activate
+uv sync                     # installs deps from pyproject.toml
+
+# Run the FastAPI server from root
+uv run python api/app.py
+```
 
 </details>
 
 <details>
   <summary>🔥Setting Up for Vibe Coding Success </summary>
 
-While it is a bit counter-intuitive to set things up before jumping into vibe-coding - it's important to remember that there exists a gradient betweeen AI-Assisted Development and Vibe-Coding. We're only reaching *slightly* into AI-Assisted Development for this challenge, but it's worth it!
+While it is a bit counter-intuitive to set things up before jumping into vibe-coding - it's important to remember that there exists a gradient betweeen AI-Assisted Development and Vibe-Coding. We're only reaching _slightly_ into AI-Assisted Development for this challenge, but it's worth it!
 
 1. Check out the rules in `.cursor/rules/` and add theme-ing information like colour schemes in `frontend-rule.mdc`! You can be as expressive as you'd like in these rules!
-2. We're going to index some docs to make our application more likely to succeed. To do this - we're going to start with `CTRL+SHIFT+P` (or `CMD+SHIFT+P` on Mac) and we're going to type "custom doc" into the search bar. 
+2. We're going to index some docs to make our application more likely to succeed. To do this - we're going to start with `CTRL+SHIFT+P` (or `CMD+SHIFT+P` on Mac) and we're going to type "custom doc" into the search bar.
+
+   ![image](https://i.imgur.com/ILx3hZu.png)
 
-     ![image](https://i.imgur.com/ILx3hZu.png)
 3. We're then going to copy and paste `https://nextjs.org/docs` into the prompt.
 
-     ![image](https://i.imgur.com/psBjpQd.png)
+   ![image](https://i.imgur.com/psBjpQd.png)
 
 4. We're then going to use the default configs to add these docs to our available and indexed documents.
 
-     ![image](https://i.imgur.com/LULLeaF.png)
+   ![image](https://i.imgur.com/LULLeaF.png)
 
 5. After that - you will do the same with Vercel's documentation. After which you should see:
 
-     ![image](https://i.imgur.com/hjyXhhC.png) 
+   ![image](https://i.imgur.com/hjyXhhC.png)
 
 </details>
 
 <details>
   <summary>😎 Vibe Coding a Front End for the FastAPI Backend</summary>
 
-1. Use `Command-L` or `CTRL-L` to open the Cursor chat console. 
+1. Use `Command-L` or `CTRL-L` to open the Cursor chat console.
 
 2. Set the chat settings to the following:
 
-     ![image](https://i.imgur.com/LSgRSgF.png)
+   ![image](https://i.imgur.com/LSgRSgF.png)
 
 3. Ask Cursor to create a frontend for your application. Iterate as much as you like!
 
-4. Run the frontend using the instructions Cursor provided. 
+4. Run the frontend using the instructions Cursor provided.
 
 > NOTE: If you run into any errors, copy and paste them back into the Cursor chat window - and ask Cursor to fix them!
 
@@ -134,19 +147,19 @@ While it is a bit counter-intuitive to set things up before jumping into vibe-co
 
 3. Run the command:
 
-     ```bash
-     npm install -g vercel
-     ```
+   ```bash
+   npm install -g vercel
+   ```
 
 4. Run the command:
 
-     ```bash
-     vercel
-     ```
+   ```bash
+   vercel
+   ```
 
 5. Follow the in-terminal instructions. (Below is an example of what you will see!)
 
-     ![image](https://i.imgur.com/D1iKGCq.png)
+   ![image](https://i.imgur.com/D1iKGCq.png)
 
 6. Once the build is completed - head to the provided link and try out your app!
 
@@ -156,13 +169,13 @@ While it is a bit counter-intuitive to set things up before jumping into vibe-co
 
 ### Vercel Link to Share
 
-You'll want to make sure you share you *domains* hyperlink to ensure people can access your app!
+You'll want to make sure you share you _domains_ hyperlink to ensure people can access your app!
 
 ![image](https://i.imgur.com/mpXIgIz.png)
 
 > NOTE: Test this is the public link by trying to open your newly deployed site in an Incognito browser tab!
 
-### 🎉 Congratulations! 
+### 🎉 Congratulations!
 
 You just deployed your first LLM-powered application! 🚀🚀🚀 Get on linkedin and post your results and experience! Make sure to tag us at @AIMakerspace!
 
@@ -182,5 +195,5 @@ Looking forward to building with the community! 🙌✨ Here's to many more cre
 
 Who else is diving into the world of AI? Let's connect! 🌐💡
 
-#FirstLLMApp 
+#FirstLLMApp
 ```

aimakerspace/aimakerspace

@@ -0,0 +1 @@
+/Users/amanz/Documents/the-ai-engineer-challenge/aimakerspace