Skip to content
JHipster Registry, based on Spring Cloud Netflix Eureka and Spring Cloud Config
Branch: master
Clone or download
Pull request Compare This branch is 1 commit ahead, 245 commits behind jhipster:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
.mvn/wrapper
central-config
src
webpack
.angular-cli.json
.dockerignore
.editorconfig
.gitattributes
.gitignore
.travis.yml
.yo-rc.json
CONTRIBUTING.md
Dockerfile
LICENSE.txt
NOTICE
Procfile
README.md
app.json
mvnw
mvnw.cmd
package.json
pom.xml
postcss.config.js
proxy.conf.json
tsconfig-aot.json
tsconfig.json
tslint.json
yarn.lock

README.md

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
You can’t perform that action at this time.