How bluedotimpact/bluedot works
Project type and purpose
• This is a monorepo hosting a suite of full‐stack microservices and shared libraries for BlueDot Impact’s custom software. Each “app” under apps/ (e.g. website, availability, meet, course-demos, proxies, Keycloak login, a standalone Node backend) is its own Dockerized service built primarily with Next.js (React + serverless API routes) or Node.js.
• The libraries/ folder holds shared TypeScript packages (UI components, configs, tooling scripts).
• The apps/infra/ folder uses Pulumi to declare and deploy a Kubernetes cluster (ingress, cert‐manager, services, persistent volumes, secrets) on Vultr.
High-level file structure analysis
• Top‐level folders:
• apps/ – twelve+ front-end/API apps plus a Node backend and Pulumi infra.
• libraries/ – shared UI, lint and TS configurations, docker‐scripts, backend contracts, etc.
• .github/, .devcontainer/, CI/CD workflows, root package.json configure the monorepo, Turbo, GitHub Actions.
• Each app follows the same pattern:
• Dockerfile – multi-stage build.
• src/pages – Next.js pages and API routes.
• src/lib/api/db & migrations – database clients (Postgres via Kysely/Kanel) or Airtable.
• src/lib/api/makeApiRoute + zod validation.
• src/components – React UI (with shared libraries/ui).
• .env.* – environment configuration.
• apps/backend is a standalone Node server with a routes plugin, auth/error plugins, DB migrations.
• apps/infra contains Pulumi code to define k8s resources (Ingress, Services, PVCs, Secrets) and Vultr VKE.
README insights
• Each app is deployed as a Docker container into Kubernetes via Pulumi.
• Primary data store: Airtable (closed source), sometimes Postgres.
• Auth: Keycloak (apps/login) with an account‐proxy. JWT/OIDC flows.
• Proxies: nginx reverse proxies (website-proxy, posthog-proxy, miniextensions-proxy) to route traffic & handle migrations.
• CI/CD: GitHub Actions for build, test, CD; libraries/docker-scripts for multi-stage deploy.