Skip to content

JHipster Registry, based on Spring Cloud Netflix Eureka and Spring Cloud Config

License

Notifications You must be signed in to change notification settings

fightingBilling/jhipster-registry

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

JHipster Registry

Build Status Docker Pulls

This is the JHipster registry service, based on Spring Cloud Netflix, Eureka and Spring Cloud Config.

Full documentation is available on the JHipster documentation for microservices.

Deploy to Heroku

Click this button to deploy your own instance of the registry:

Deploy to Heroku

There are a few limitations when deploying to Heroku.

  • The registry will only work with native configuration (and not Git config).
  • The registry service cannot be scaled up to multiple dynos to provide redundancy. You must deploy multiple applications (i.e. click the button more than once). This is because Eureka requires distinct URLs to synchronize in-memory state between instances.

Running locally

To run the cloned repository;

  • For development run ./mvnw -Pdev,webpack to just start in development or run ./mvnw and run yarn && yarn start for hot reload of client side code.
  • For production profile run ./mvnw -Pprod

About

JHipster Registry, based on Spring Cloud Netflix Eureka and Spring Cloud Config

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Java 29.2%
  • CSS 27.1%
  • TypeScript 24.9%
  • HTML 14.1%
  • JavaScript 2.5%
  • Shell 1.3%
  • Batchfile 0.9%