How ubclaunchpad/forum works
Project type and purpose
• This is a full-stack web and desktop application (“ForumAI”) combining a Next.js/Tauri front end, a Supabase-backed API layer (Deno Edge Functions), a Postgres database, and AI services (OpenAI + custom Deno “model” runners).
• Its purpose is to power structured academic discussion forums with AI assistance, user authentication, file storage, and real-time interactions.
File structure
• Top-level directories:
• frontend – Next.js (App Router) + Tauri integration for desktop builds
• server – Supabase Edge Functions written in Deno, organized by domain (courses, posts, users, documents, search, analytics, status) plus migrations/seed files for Postgres
• model – standalone Deno scripts (embed.ts, report.ts) for AI workflows (embeddings, report generation)
• shared – Deno module with shared schemas, types and utilities consumed by server & model
• Key patterns:
• Monorepo separation of concerns (frontend vs. API vs. model vs. shared code)
• BFF (Backend-For-Frontend) approach via Supabase Edge Functions
• Next.js App Router with React contexts/providers for state management
• Config & deployment files: Dockerfiles (frontend, model), deno.json/lock for server/model/shared, Supabase config.toml, migrations, GitHub workflows.
README
• Confirms core stack: Next.js, Supabase (Auth, Edge Functions, Storage, Postgres), Deno for tests and edge functions, OpenAI API for AI assistance
• Outlines developer setup: environment variables, Supabase CLI commands, Deno test commands