How t4ko0522/connectix2 works
Project type and purpose
• Connectix2 is a full-stack, containerized Next.js 15 application (React 18 + TypeScript) that provides a profile-creation platform tailored for VRChat users.
• It uses SSR/SSG for performance, custom API routes for authentication and profile management, and integrates with external services (Supabase, VRChat API, email).
Main architectural components
A. User’s Web Browser
• Issues HTTP requests to pages & API endpoints; renders React-driven UI.
B. Next.js Application (deployed in AWS EKS / Kubernetes)
• Frontend (app/* & components/*): SSR/SSG pages, client-side React.
• Backend (app/api/*): Node.js API routes handling login, signup, password reset, VRChat OAuth, 2FA, etc.
• Shared libraries (lib/): supabaseClient.ts (DB/auth), sendMail.ts (email), utils.
C. Supabase (External Service)
• PostgreSQL database, authentication, storage (if used).
D. VRChat API (External OAuth Service)
• Handles user login, token verification, 2FA workflows.
E. Email Delivery Service (SMTP or 3rd-party API)
• Accepts requests from sendMail.ts to dispatch verification & reset emails.
Relationships & data flows
1. User → Next.js Frontend
• Requests a profile or dashboard page → served via SSR or SSG.
2. Frontend → Next.js API
• On signup/login/password reset → fetch() calls to /api/auth/* routes.
3. API → Supabase
• Reads/writes user records, session tokens, profile data.
4. API → VRChat API
• Performs OAuth login flows, 2FA verification.
5. API → Email Service
• Triggers signup verification & reset emails.
6. Supabase/Database → API → Frontend
• Returns user data, links, settings for rendering.
Architectural patterns & design principles
• File-based routing (Next.js “app” directory) separates page-level concerns.
• API routes co-located with frontend for single monorepo, single container.
• Contexts/hooks (contexts/, hooks/) for global state management (loading, toast notifications).
• shadcn/ui + Radix + Tailwind for design system (components/ui/*).
• SSR/SSG for SEO and performance.
• Containerized deployment on Kubernetes for scalability and resilience.
Technologies & frameworks to call out
• Next.js 15 (React 18), TypeScript
• Supabase (client & DB)
• Node.js API routes
• Tailwind CSS, shadcn/ui, Radix UI
• AWS EKS + Kubernetes, GitHub Actions/CodePipeline (CI/CD)
• External APIs: VRChat OAuth, Email service (SMTP/SendGrid)
Final checklist
• Clear labels on every component and folder cluster.
• Notes on SSR/SSG, CI/CD, and container deployment.