JHipster Registry

JHipster Registry is a service-discovery and configuration server for JHipster microservice applications.

  • Infrastructure
  • Monitoring & Logging
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

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

44/100 Fair

Maintained
40last commit 325 days ago
Popular
57713 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
56no serious findings, 25 minor, CI, tests, OpenSSF Scorecard 3.4/10

Based on 4 of 5 factors.

GitHub stars
713
Open issues
13
Last commit
2025-12-31
Latest release
v7.5.0
License
Apache-2.0
Activity
stale

Checked 3 days ago - source: GitHub (jhipster/jhipster-registry)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start Registry in a microservices stack If your project is a microservices setup (many small services instead of one big app), use the production Docker Compose file (a recipe that starts multiple packaged services together) to launch JHipster Registry and related services. Without Registry running, other services may not be able to find each other. source
  • Start Keycloak if login uses it If your app is configured to use Keycloak for sign-in, run the project's provided npm (JavaScript package manager) command that starts the Keycloak Docker container (a packaged sign-in service). Without it running, users may be unable to log in securely. source
  • Set up HTTPS for public access If you expose the app with a public domain name, install Apache (a web server) and Certbot, then put your domain and email into the Let's Encrypt command. This gives visitors trusted HTTPS instead of browser warnings. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

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.

Answers sourced from github.com, stackoverflow.com, stackoverflow.com

Community

Collected 48 days ago - public community threads