Description

This PR optimizes the Docker infrastructure for production by implementing a multi-stage Docker build. The motivation is to drastically reduce the size and increase the security of the final Docker image by serving purely static files via Nginx, rather than running a Node.js development server with source code included.
Fixes #1869

Type of Change

• New feature (e.g., new page, component, or functionality)
• Bug fix (non-breaking change that fixes an issue)
• UI/UX improvement (design, layout, or styling updates)
• Performance optimization (e.g., code splitting, caching)
• Documentation update (README, contribution guidelines, etc.)
• Other (please specify): DevOps / Infrastructure Enhancement

Changes Made

• Dockerfile: Replaced the single-stage development image with a robust two-stage build.
  • Stage 1 (builder): Uses node:22-alpine to install dependencies and run npm run build.
  • Stage 2 (production): Uses nginx:alpine to copy only the compiled static assets (/build) and serves them.
• docker-compose.yml: Added target: builder to the build block. This ensures that developers running docker-compose up locally still get the development environment with hot-reloading (npm run dev) and are unaffected by the production stage.

Dependencies

• No new external dependencies.
• Confirmed the Dockerfile builder stage uses node:22-alpine to align with the >=20.9.0 <23 engine requirement in package.json and the .nvmrc configuration.

Checklist

• My code follows the style guidelines of this project.
• I have tested my changes across major browsers and devices
• My changes do not generate new console warnings or errors .
• I ran npm run build and attached screenshot(s) in this PR.
• This is already assigned Issue to me, not an unassigned issue.

Request

• Please add valuable lables to the PR so that it helps me, to get good points for contribution in GSSoC, Thankyou @sanjay-kv