How modelearth/team works
Project Type and Purpose
• MemberCommons is a full-stack JAM Stack collaboration platform.
• The frontend is purely static (HTML/CSS/vanilla JS). The backend is a Rust monolith (Actix-web + SQLx) exposing a JSON/REST API.
• It integrates a PostgreSQL database (SuiteCRM schema) and external AI services (Google Gemini) and OAuth providers for authentication.
File-Structure Analysis
• Top-level “css/”, “js/”, “img/”, “index.html” etc. → static frontend.
• “src/” folder with Cargo.toml and Rust files → back-end service using Actix-web.
• “admin/”, “projects/”, “preferences/” → static sub-apps or modules served by the same static host.
• “config/settings.example.js” & “.env.example” → runtime configuration for API endpoints, OAuth, DB URLs.
• “sql/” scripts → DB schema and utility SQL.
• No separate microservices—common monolith with modular Rust source files (main.rs, import.rs, recommendations.rs, insights.rs).
Key Insights from README
• Frontend: Static hosting, no bundler, mobile-first responsive design, pure JS modules for search, projects, surveys.
• Backend: Actix-web routes, SQLx for async Postgres, JWT + OAuth for auth.
• AI: Google Gemini queries from backend or via JS client (through backend proxy).
• DB: PostgreSQL on Azure/Google Cloud, SuiteCRM schema for contacts/projects.