How wfp-vam/dmp works
Project type and purpose
• This is a full-stack, monorepo-style form management tool (“DMP”) built for the World Food Programme Cambodia.
• It consists of three primary “apps”:
• apps/frontend – a Next.js/React UI for users to log in, fill and review disaster-related forms
• apps/backend – a NestJS REST API for authentication, user & campaign management, form persistence, and webhook handling
• apps/backend-infrastructure – an AWS CDK stack provisioning VPC, ECS services, RDS, certificates, Route53 records, etc.
• Shared TypeScript definitions live under packages/interfaces; linting, CI/CD configs and scripts at the root.
File structure
• Top-level directories:
• apps/ – frontend, backend code and infra
• packages/ – shared configs and interfaces
• .github/workflows – CI pipelines for lint, test, staging & production merges
• turbo.json, pnpm-workspace.yaml – orchestrate monorepo builds
• apps/backend:
• NestJS modules: auth, user, kob o integrations, webhook, logger
• datasource & TypeORM migrations targeting an RDS database
• Dockerfile + docker-compose for local development
• apps/frontend:
• Next.js pages & components implementing forms, reports, filters
• React Query or SWR hooks under services/api
• Environment management for production, staging, test
• docs under apps/frontend/docs describing architecture, deploy, error handling
• apps/backend-infrastructure:
• CDK constructs for network (VPC), container clusters (ECS service), database (RDS), certificates, DNS
README.md
• High-level description: “form management tool” for disaster relief
• Instructions defer into backend README for more details