Skip to main content

BeWith repo map

Overview​

BeWith's product spans about 18 active repos plus several dead ones. This skill is the map of what each repo does and what it talks to, so new work lands in the right repo instead of duplicating something that already exists elsewhere, extending a path that's being retired, or targeting dead infrastructure.

Read references/repos.md for the full per-repo breakdown — what each repo is, what it depends on, and what depends on it.

At a glance​

  • Consumer-facing: superco-consumer (legacy PHP, owns its own SQL) is the main end-user app; consumer-mobile (Flutter, one app per city) and leaders-app (ticket scanning) are the mobile side.
  • Backoffice, for customer (org) admins — B2B2C: organization-dashboard is current; superco-management ("Shemi") is the deprecated predecessor being phased out.
  • Central backend: backend-services — the only owner of MongoDB (Mongoose) and the newer SQL tables (TypeORM). Nearly everything calls it; the exception is superco-consumer's own legacy SQL access, which predates it.
  • Embedded / iframe apps: management-webapp (iframes shown inside superco-consumer, and some embedded directly on a customer's own external website) and facility-rentals (seat-map booking, iframed into superco-consumer during event registration).
  • Standalone: partner-portal (partner onboarding, linked to — not embedded — from superco-consumer), support-tool-frontend (internal, support-team-only, super-admin access).
  • Shared packages, not services: design-system, with-calendar, feature-flags — all @bewith-dev/* npm packages consumed by multiple frontends/backends.
  • Infra: IAC-Terraform (live, AWS resource provisioning) and Kubernetes-deployments (live, GitOps — two branches, one per EKS environment).

Deprecated / dead — don't build on these​

  • superco-management — deprecated, replaced by organization-dashboard; migration nearly done.
  • pulumi/ (a folder inside Kubernetes-deployments, not its own repo) — removed from main on 2026-08-03, but still alive on the staging branch and still attracts dependabot PRs. Nothing applies it; a queue once declared there was never actually created.
  • with-terraform, cdk-infra, infrastructure, deployment — four standalone infra repos, all fully dead since 2022–2023. Not part of the ~18 active repos above, but they look plausible at a glance, which is exactly the trap.
  • sqs-consumer — not dead yet, but both of its roles (single-instance schedule triggers, SQS queue forwarding) are actively being migrated into backend-services.

For environment-by-environment infra detail — which branch/file each deployment actually reads, live-vs-dead evidence, and commands to re-verify — see the bewith-provision-sqs-queue skill's references/environments-and-repos.md. That file is the more detailed, actively re-verified source for infra specifics; this skill points there rather than duplicating it.