Containerise backend with Dockerfile and docker-compose for local dev

[GavT]

Summary

There is no Dockerfile for the backend. Deployment is manual and environment setup is undocumented.

What to create

Dockerfile:

FROM eclipse-temurin:17-jre-alpine
WORKDIR /app
COPY backend/build/libs/backend-all.jar app.jar
ENV PORT=5000
EXPOSE 5000
ENTRYPOINT ["java", "-jar", "app.jar"]

docker-compose.yml (local dev):

services:
  backend:
    build: .
    ports: ["5000:5000"]
    environment:
      FUEL_FINDER_CLIENT_ID: ${FUEL_FINDER_CLIENT_ID}
      FUEL_FINDER_CLIENT_SECRET: ${FUEL_FINDER_CLIENT_SECRET}
      KTOR_ENV: dev

Also

• Add .dockerignore
• Document deployment steps in README.md
• Add Docker build to CI workflow

Workstream: WS3 Phase 3A

[GavT]

Status update — EB deploy is now the canonical path

PR #22 codified the Elastic Beanstalk deployment flow: ./gradlew ebBundle produces a ZIP containing the shadowJar + Procfile + .platform/ config, which is uploaded to EB. Containerisation is not on the critical path for production.

The remaining case for this issue is local development consistency (a single docker compose up to run the backend, the laptop ingester, and maybe a future test fixture). That's still useful but lower priority than the security and operational items.

Setting P3. Could also reasonably be closed as wontfix if the team commits to JAR-on-EB long-term; leaving open for now in case the local-dev angle is wanted.