How abcall-project/abcall-web works
Project type and purpose
• This is a single‐page application (SPA) built with Angular (TypeScript) for managing call‐center issues for corporate clients.
• It’s purely a front‐end repo, with environment configs pointing at REST API endpoints (issues, customers, users, payments, predictive/AI services).
• It includes Docker and Kubernetes manifests for containerized deployment, plus GitHub Actions CI/CD and a Netlify preview pipeline.
File structure
• src/ – Angular application code
• app/ – feature modules (authentication, pages, guards, interceptors, layouts, services, pipes, models)
• assets/ – static assets (images, i18n JSON, SCSS styling)
• environments/ – per‐feature environment configurations (environment.issues.ts, environment.customers.ts, etc.)
• main.ts, index.html – Angular bootstrap
• docker/ & Dockerfile & develop.Dockerfile – build images for production and development
• docker-compose*.yaml – local multi‐container setup with Nginx serving the built SPA
• kubernetes/ – manifests for ConfigMap, Secrets, Deployment, Service, Ingress, HPA
• .github/workflows/ – GitHub Actions for lint/test, merge to develop, release to main
• netlify.toml – Netlify hosting configuration
README for additional insights
• Confirms Angular/TypeScript/Node tech stack
• Mentions web app “to manage call center issues”
Detail without overthinking
• At a minimum, break out:
• Client Browser
• Hosting (Nginx container in K8s/Netlify)
• Angular Modules (Authentication, Pages, Services)
• External REST APIs (issues/customers/users/payment/predictive)
• CI/CD pipeline and Kubernetes cluster
• Optionally, annotate environment configs (environment.issues.ts etc.) to show how endpoints are wired.
Layer 1 – Logical Architecture (SPA modules + external APIs)
Layer 2 – Deployment Architecture (CI/CD → Docker → K8s → Ingress → Nginx → Browser)