How onearmy/community-platform works
Project type and purpose
• This is a full-stack, monorepo community platform (Remix/React front-end + Node/Remix server + multiple back-end components) whose goal is to provide forums, maps, libraries and collaboration tools to global communities. It uses Supabase as its primary database/auth/storage, Firebase Cloud Functions for background processing and real-time services, and a suite of custom services/integrations (Slack, Discord).
File structure
• Top-level “src” directory: contains the Remix front-end (React/TSX), server entry points, route handlers (api.*).
• “functions”: Firebase Cloud Functions (TypeScript) for scheduled tasks, email notifications, database exports, integrations, aggregations, alerting.
• “supabase”: a separate Supabase Functions folder (Deno) plus SQL migration scripts—they represent a second back-end microservice.
• “shared”: shared TypeScript models & utilities consumed by both front-end and back-ends.
• “packages”: design system (“components”), testing (“cypress”), documentation, themes, simulated-webhook-receiver.
• “containerization” & Dockerfiles/docker-compose: local dev and CI deployment artifacts.
• CI/CD config (.circleci, GitHub Actions, Fly.io toml) and various scripts for build, deploy, local-dev.
README
• Confirms the stack: Remix + React front-end, Node-based SSR back-end, Supabase (Postgres + Auth + Storage), Firebase (Auth emulator, Firestore, Realtime DB, Storage), cloud functions, GitPod/CircleCI/Fly.io deployment.
• Points to docs on “remix.md”, “supabase.md” and “firebase-emulator.md” describing local emulation and architecture.