This project uses Docker to containerize both the frontend and backend, enabling consistent builds and simplified deployment. Each service is defined with a multi-stage Dockerfile to optimize image size and build performance.

Backend (docker/backend.dockerfile)

The backend is a Spring Boot application built with Gradle and JDK 17. Its Dockerfile is split into two stages:

1. Build Stage (gradle:8.3-jdk17):
   • Caches Gradle dependencies early for faster rebuilds.
   • Compiles the backend using bootJar, skipping tests for speed.
2. Runtime Stage (eclipse-temurin:17-jre):
   • Copies the built .jar from the previous stage.
   • Uses ENV SPRING_PROFILES_ACTIVE=docker for environment flexibility.
   • Exposes port 8080 and runs the app via java -jar.

Frontend (docker/frontend.dockerfile)

The frontend is a Vite-based React application served by Nginx. Its Dockerfile also uses two stages:

1. Build Stage (node:22-alpine):
   • Installs dependencies with Yarn using a frozen lockfile for reproducibility.
   • Runs yarn build to produce static assets.
2. Runtime Stage (nginx:alpine):
   • Replaces the default Nginx config with a custom one (docker/nginx.conf).
   • Serves static files from /usr/share/nginx/html.
   • Exposes port 80 and starts Nginx in the foreground.

Nginx Configuration (docker/nginx.conf)

The custom Nginx config serves the frontend and proxies API calls to the backend:

• Frontend:
  • Uses try_files to support client-side routing via index.html.
  • Serves built assets from the Vite dist/ directory.
• API Proxying:
  • Routes requests starting with /api/ to the backend container (http://backend:8080/api/).
  • Forwards relevant headers to maintain client context.
  • Ensures compatibility by using HTTP/1.1 with keep-alive.