Automate microservice installation

[akulamartin]

Overview of the feature request

I have to do the following to run a microservice:

spring:
docker:
compose:
enabled: false

in app and app-dev.yml

in pom.xml

org.postgresql
postgresql
runtime

docker compose the jhipster registry
docker compose -f jhipster-registry.yml up -d

Motivation for or Use Case

It makes it easier to run microservices.

[theantiz]

Hitting this as well and it's not really an edge case.

Any real microservice stack (gateway + N services) generated with spring.docker.compose.enabled: true runs into this by default: every service ships its own postgresql.yml, and each tries to boot its own Postgres container on startup. They all attempt to bind the same port and collide immediately.

Workaround that gets multi-app local development working:

application.yml / application-dev.yml:
```yaml
spring:
docker:
compose:
enabled: false
```

pom.xml:
```xml

org.postgresql
postgresql
runtime

```

Start Postgres and the registry manually:
```bash
docker compose -f jhipster-registry.yml up -d
```

This resolves the conflict, but it's currently a manual patch that every team building a microservice stack has to independently rediscover. #27703 and #27685 report the same underlying symptom, so this isn't an isolated setup issue — it's a pattern.

Proposed fix: have the generator apply this configuration by default for microservice apps on PostgreSQL, rather than leaving it as an undocumented follow-up step.

Happy to help test a PR if that would move this along faster than tracking it purely as an issue.

[shashikant-38]

I'd like to work on this issue. I'll first reproduce the PostgreSQL/Docker Compose setup locally and investigate where the microservice configuration is generated.