How ifpbesp/apae works
Project type and purpose
• From the README we see “APAE” consists of two systems:
• A Patient Management System (for internal use by APAE staff)
• An Information Display System (for public or stakeholder consumption)
• The project appears to be a full-stack solution, likely including:
• A web frontend (React/Vue/Angular or similar)
• A mobile app (Android/iOS, possibly React Native/Flutter)
• A backend REST/GraphQL API
• A database (relational or document)
• CI/CD pipelines and DevOps infrastructure
File structure
• At this moment the repository only contains README.md, but the conventions and labels imply the following top-level directories in time:
/backend
/frontend-web
/frontend-mobile
/docs
/infrastructure (Docker, k8s, Terraform)
/tests (unit, integration, e2e)
• Configuration and orchestration files (Dockerfile, docker-compose.yml, k8s manifests, Terraform .tf files) will live under /infrastructure
README for additional insights
• Commit and branch conventions show separate scopes for auth, database, api, service, repository, cache (backend) and ui, components, layout, state (frontend).
• GitFlow labels and Kanban lanes reveal a well-structured CI/CD process and the presence of multiple deployment environments: development, homologation (staging), production.