How nitheeshp-irl/microservice-frontend works
Project type and purpose
• This is a full‑stack Node.js web application built with Express.
• It serves both static assets (in public/) and dynamic pages via EJS templates (in views/).
• It includes a CI pipeline (.github/workflows/docker-ci.yml) and Kubernetes manifests (k8/) for containerized deployment.
File structure
• Top‑level:
• app.js – Express application entry point
• routes/ – route handlers (index.js, origamis.js)
• public/ – static assets (CSS, images, client JS)
• views/ – EJS templates
• Dockerfile – container image build instructions
• k8/ – Kubernetes base manifests and overlays for environment‑specific deployments
• .github/workflows – CI that builds and tests Docker image
• Config & dependencies:
• config.json – application configuration
• package.json – npm dependencies and scripts
• test/ – integration/unit tests (e.g. appTest.js)
README
• Specifies Node version, build & launch commands, and default port (3000).
• Confirms it’s a simple Express‑based frontend app.
Detailed capture of architectural elements
• Under “Express Pod”, break down subcomponents:
• Static file server (serves /public)
• Route handlers (/, /origamis)
• Template engine (EJS in views/)
• Config loader (config.json)
• Under “CI/CD”, show steps: checkout → npm install → test → Docker build → push → Kustomize apply
• Under “Kubernetes”, show base manifests plus overlays/development customizing namespace or replica count