How 66my/gitdiagram works
Main Components
• Database: A PostgreSQL instance managed by Drizzle ORM (configuration and schema found under src/server/db) that stores any persistent data required.
• External Integrations:
• GitHub: To obtain repository data (both public and private).
• Additional services such as API analytics (PostHog, Api-Analytics) and possibly GitHub Actions for CI/CD.
• Deployment & DevOps: Docker (Dockerfile, docker-compose.yml, and deployment scripts for backend) and Nginx (located under backend/nginx) used to containerize and route requests. CI/CD is powered by GitHub Actions (see .github/workflows).
Mapping Relationships and Interactions
• Frontend sends requests (via API calls) to the Backend.
• The Backend fetches repository structures from GitHub, processes the data (via various services and prompts), and accesses the Database if necessary.
• Flow from a user’s browser to the frontend, API, external services (GitHub and AI), and then back.
Architectural Patterns
• Modular separation within the backend:
• Routers (defining API endpoints),
• Services (handling business logic and external API interactions), and
• Utilities (supporting functions like format_message).
• For the frontend, note the component-based structure (components, hooks, lib, and server directories) typical of Next.js applications.
With Technologies & Frameworks
• Next.js, TypeScript, Tailwind CSS, and ShadCN for the frontend.
• FastAPI, Python, and Server Actions in the backend.
• PostgreSQL managed via Drizzle ORM for database management.
• Docker, Nginx, and GitHub Actions for deployment and CI/CD.
• External integrations: GitHub APIs and AI services (OpenAI o3-mini / Anthropic API).