Deploying Finovara on Docker and fixing a critical bug.
I recently decided to move my Spring Boot app Finovara to Docker. At first it was just supposed to be a small improvement to the setup. In reality, it turned into a debugging session that took way ...

Source: DEV Community
I recently decided to move my Spring Boot app Finovara to Docker. At first it was just supposed to be a small improvement to the setup. In reality, it turned into a debugging session that took way longer than I expected. Why I even bothered with Docker There were a few reasons behind this: I wanted more control over the environment I needed a separate database (finovara-test) for automated tests I was tired of manually setting everything up locally and I wanted something closer to a real production setup Initial setup I started with a simple PostgreSQL container and connected my app to it. Here’s a simplified version of what I used: services: finovara-db: image: postgres:15 container_name: finovara-db restart: always environment: POSTGRES_DB: finovara POSTGRES_USER: postgres POSTGRES_PASSWORD: ${DB_PASSWORD} ports: - "5432:5432" healthcheck: test: ["CMD-SHELL", "pg_isready -U postgres"] interval: 5s retries: 10 Dockerfile: FROM eclipse-temurin:21-jdk WORKDIR /app COPY target/*.jar app.