Docker Compose development profile change in JHipster 8 Spring Boot 3 migration

Answer

The documented default development profile for both monolith and microservice archetypes in JHipster 8+ is dev, set via the environment variable SPRING_PROFILES_ACTIVE=dev.

Environment variables injected by the compose files

• SPRING_PROFILES_ACTIVE=dev (base)
• SPRING_CLOUD_CONFIG_URI=http://config-server:8888 (override)
• SPRING_CLOUD_GATEWAY_ROUTES may be present for gateway service, but microservices rely on config‑server.

Files that define the compatibility boundary

The boundary between JHipster 7 (Spring Boot 2) and JHipster 8+ (Spring Boot 3) is marked by two generated files:

1. .jhipster/docker-compose.yml – base compose that removed the eureka service and added gateway and config‑server services.
2. .jhipster/docker-compose.override.yml – supplies the dev‑profile environment variables (including SPRING_PROFILES_ACTIVE and SPRING_CLOUD_CONFIG_URI).

Canonical local bootstrap for microservices after Eureka deprecation

Yes. The generated compose defines a config‑server and a gateway service. A repeatable local bootstrap consists of:

1. Start config‑server (provides SPRING_CLOUD_CONFIG_URI).
2. Start gateway (Spring Cloud Gateway routes to microservices).
3. Start each microservice; it reads SPRING_PROFILES_ACTIVE=dev and SPRING_CLOUD_CONFIG_URI from the environment and registers with the gateway (or discovers via Spring Cloud Discovery if enabled).

To verify that the dev profile is active and the expected variables are present, run:

docker compose config

and inspect the output for the environment section of each service.

Missing diagnostic detail

If you are using Docker Compose v1 (the docker-compose binary) instead of the v2 docker compose command, the syntax for overrides may differ and the docker compose config command will not be available. Confirm which Docker Compose version you are using to ensure the verification step works.