This application was generated using JHipster 4.6.2, you can find documentation and help at https://jhipster.github.io/documentation-archive/v4.6.2.
This is a "uaa" application intended to be part of a microservice architecture, please refer to the Doing microservices with JHipster page of the documentation for more information.
This is also a JHipster User Account and Authentication (UAA) Server, refer to [Using UAA for Microservice Security][] for details on how to secure JHipster microservices with OAuth2. This application is configured for Service Discovery and Configuration with the JHipster-Registry. On launch, it will refuse to start if it is not able to connect to the JHipster-Registry at http://localhost:8761. For more information, read our documentation on [Service Discovery and Configuration with the JHipster-Registry][].
To start your application in the dev profile, simply run:
./gradlew
For further instructions on how to develop with JHipster, have a look at [Using JHipster in development][].
You can also use [Angular CLI][] to generate some custom client code.
For example, the following command:
ng generate component my-component
will generate few files:
create src/main/webapp/app/my-component/my-component.component.html
create src/main/webapp/app/my-component/my-component.component.ts
update src/main/webapp/app/app.module.ts
To optimize the minorpluscardportal application for production, run:
./gradlew -Pprod clean bootRepackage
To ensure everything worked, run:
java -jar build/libs/*.war
Refer to [Using JHipster in production][] for more details.
To launch your application's tests, run:
./gradlew test
Performance tests are run by Gatling and written in Scala. They're located in src/test/gatling and can be run with:
./gradlew gatlingRun
For more information, refer to the [Running tests page][].
You can use Docker to improve your JHipster development experience. A number of docker-compose configuration are available in the src/main/docker folder to launch required third party services. For example, to start a mariadb database in a docker container, run:
docker-compose -f src/main/docker/mariadb.yml up -d
To stop it and remove the container, run:
docker-compose -f src/main/docker/mariadb.yml down
You can also fully dockerize your application and all the services that it depends on. To achieve this, first build a docker image of your app by running:
./gradlew bootRepackage -Pprod buildDocker
Then run:
docker-compose -f src/main/docker/app.yml up -d
For more information refer to [Using Docker and Docker-Compose][], this page also contains information on the docker-compose sub-generator (jhipster docker-compose), which is able to generate docker configurations for one or several JHipster applications.
To configure CI for your project, run the ci-cd sub-generator (jhipster ci-cd), this will let you generate configuration files for a number of Continuous Integration systems. Consult the [Setting up Continuous Integration][] page for more information.
[Using UAA for Microservice Security]: https://jhipster.github.io/documentation-archive/v4.6.2/using-uaa/[Using JHipster in development]: https://jhipster.github.io/documentation-archive/v4.6.2/development/ [Service Discovery and Configuration with the JHipster-Registry]: https://jhipster.github.io/documentation-archive/v4.6.2/microservices-architecture/#jhipster-registry [Using Docker and Docker-Compose]: https://jhipster.github.io/documentation-archive/v4.6.2/docker-compose [Using JHipster in production]: https://jhipster.github.io/documentation-archive/v4.6.2/production/ [Running tests page]: https://jhipster.github.io/documentation-archive/v4.6.2/running-tests/ [Setting up Continuous Integration]: https://jhipster.github.io/documentation-archive/v4.6.2/setting-up-ci/