How programmingnotjustcoding/jiva works
Project Type & Purpose
• This is a full‑stack, microservices‑based application (“Jiva”) for coal‑mine operations.
• It comprises:
• Multiple backend services (auth, shift, incident, SMP, workplan, ERP, notification)
• A Next.js web frontend
• A Flutter mobile frontend
• Infrastructure definitions (Docker Compose, Terraform, init scripts)
• Goal: digital shift logs, safety‑management plan (SMP) tracking, incident/hazard reporting, notifications, dashboards.
File Structure Analysis
• Top‑level “apps” folder:
• apps/backend – one folder per microservice, each with:
– “bruno” definitions (API specs/tests)
– Drizzle migrations & schema (Postgres)
– src/api (controllers, routes, middlewares)
– src/services (business logic)
– src/config, src/database, src/utils
• apps/web – Next.js app (pages, components, layouts)
• apps/mobile – Flutter app (lib/components, services, models)
• “docker/compose” and “docker/docker-compose.yml” define local services: Postgres, MinIO, Nginx.
• “infra/main.tf” – Terraform for cloud infrastructure.
• “scripts/init-dbs.sh” – database initialization.
Key README Insights
• Shift logging/handover, SMP tasks, hazard/incident reporting, alerts, dashboards.
• Indicates domain: mining safety & productivity.