How herin7/gitforme works
Project type and purpose
• GitForMe is a full-stack, microservice-based web application whose goal is to help developers explore and understand GitHub repositories via an AI-powered dashboard and chat interface.
File structure
• Top-level directories:
• gitforme/ → Frontend (React + Vite + Tailwind + Framer Motion)
• server/ → Node.js/Express backend (authentication, GitHub API integration, business-logic controllers, Redis client)
• llm-server/→ Python/Flask microservice (vector embedding, FAISS index, Azure OpenAI orchestration)
• Supporting files and configs:
• .github/workflows → CI/CD on GitHub Actions, deploy to Azure Static Web Apps
• Dockerfile in llm-server → container for LLM microservice
• Staticwebapp.config.json, azure workflows → Azure deployment
README for additional insights
• Microservice architecture: Frontend, Backend, LLM server
• Tech stack explicitly listed under “How It Works: Architecture”
• External dependencies: GitHub OAuth, Azure OpenAI, FAISS
Detail without overthinking
• Break each microservice into its critical components (e.g., Node.js: Controllers, Routes, Middlewares)
• Every external interaction: OAuth handshakes, API calls, embedding/storage steps.
• Essential cross-service contracts: REST endpoints, message formats, streaming flows.