# JHipster Registry

JHipster Registry is a service-discovery and configuration server for JHipster microservice applications. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5405/jhipster-registry

## Description

JHipster Registry is a service-discovery and configuration server for JHipster microservice applications. It lets each microservice discover and communicate with the others through Eureka, centralises application configuration via Spring Cloud Config, and exposes a Spring Boot Admin dashboard so operators can monitor performance and update settings across the stack. It is for teams deploying JHipster-generated microservices and want a single point of control.

## Platform availability

Available on 0 of 10 platforms.

## Health score

44/100 (Fair), based on 4 of 5 factors.
- Maintained: 40 (last commit 325 days ago)
- Popular: 57 (713 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Security check: 56 (no serious findings, 25 minor, CI, tests, OpenSSF Scorecard 3.4/10)

## Links

- GitHub: https://github.com/jhipster/jhipster-registry
- Docker Hub: https://hub.docker.com/r/jhipster/jhipster-registry

## Common questions

### How can I connect JHipster Registry to microservices when running it from Docker?

Run JHipster Registry from Docker and attach the microservices to the same Docker network overlay so they can resolve the registry.

### Does JHipster Registry persist its data by default?

No. Its default integration uses a vault server with an in-memory backend, so data should not be persisted.

### How do I secure the Jasypt password in JHipster Registry configuration?

Encrypt the Jasypt password property in the registry configuration.

---
Source: Our Local Host (https://ourlocalhost.com/app/5405/jhipster-registry), the self-hosted and open-source app directory.
