How vicelikedust/gitdiagram works
Main Components
a) Client-Side (Frontend):
• Next.js Application Layer
• Pages and Routes (src/app directory)
• Components (src/components)
• Server Actions (src/app/_actions)
• Database Integration (src/server/db)
b) Server-Side (Backend):
• FastAPI Application
• Core Services
• API Routers
• Rate Limiter
• Nginx Reverse Proxy
c) External Services:
• Claude 3.5 Sonnet AI
• GitHub API
• PostgreSQL Database
• Analytics Services (PostHog, Api-Analytics)
[Client Layer]
• ↕️
[API/Backend Layer]
• ↕️
[External Services Layer]
Component Relationships
• Backend → Claude AI (for processing repository data)
• Backend → GitHub API (for fetching repository information)
• Frontend ↔️ PostgreSQL (via server actions for data persistence)
• Backend → Rate Limiter (for request throttling)
Specific Implementation Details
Frontend Section:
• Next.js app structure with pages, components, and server actions
• TypeScript and Tailwind CSS layers
Backend Section:
• FastAPI routes (/generate, /modify)
• Nginx reverse proxy configuration
• Rate limiting boundaries
• Service integrations (Claude, GitHub)
Database Section:
• PostgreSQL with Drizzle ORM connection
• Schema relationships if applicable
Deployment Architecture
Deployment information:
• Vercel (Frontend hosting)
• EC2 (Backend hosting)
• Docker container boundaries
• GitHub Actions CI/CD pipeline
Additional Elements
• Version/environment indicators
• Security boundaries and API key requirements
• Rate limit thresholds