How bndkt/sharemystack works
Main Components
• Frontend:
• Mobile App (React Native via Expo + Expo Router)
• Web Landing (Remix app deployed on Cloudflare)
• Sanity Studio (CMS for editorial content)
• Remotion Video Generator (marketing assets)
• Shared Assets & Scripts:
• Static JSON data (assets/data)
• Seed-data GitHub Action (packages/seed-data-action)
• Backend & Infrastructure:
• Supabase (PostgreSQL + Storage + Functions)
• GitHub Actions (CI/CD workflows under .github/workflows)
• External Services: OneSignal (push), Sentry (error tracking), Vexo (analytics)
Component Roles & Relationships
• Mobile App
• Offline-first: WatermelonDB local store synchronized via Supabase push/pull functions
• Auth via Supabase; real-time sync, file uploads to Supabase Storage
• Uses OneSignal, Sentry, analytics hooks
• Web Landing (Remix)
• Reads public data from Supabase via REST/JS SDK
• Hosts marketing site, generates OG images, QRCodes
• Sanity Studio
• CMS for editorial content (tools, tutorials)
• Deploys to a CDN or Vercel (not in repo, but typical)
• Remotion Video
• Pulls static data (from assets/data or Supabase)
• Renders marketing videos offline
• Seed-Data Action
• GitHub Action that reads assets/data, writes into Supabase tables via its SDK
• Run on schedule or manually to seed / update static data
• Supabase
• PostgreSQL database with tables: profiles, tools, stacks, picks, stars, categorization, etc.
• RPC functions: push, pull, create/update profiles, manage slugs, sync views
Important Architectural Patterns & Principles
• Monorepo managed by Turbo/Turborepo (turbo.json)
• Full-stack separation: each app in apps/*; shared logic in packages/* or assets/*
• Offline-First Sync: local DB + remote push/pull via SQL functions
• CI/CD via GitHub Actions: separate workflows for building mobile, web preview, production, seed data
• CMS as a decoupled editorial service (Sanity)