Playground and test driver application - Part of a leanovate interpretation of Contoso's Conference Manager
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
gradle
src
.editorconfig
.gitattributes
.gitignore
.travis.yml
.yo-rc.json
Jenkinsfile
LICENSE
README.md
build.gradle
gradle.properties
gradlew
gradlew.bat
package.json
settings.gradle
yarn.lock

README.md

contoso

This application was generated using JHipster 4.0.3, you can find documentation and help at https://jhipster.github.io/documentation-archive/v4.0.3.

This is a "microservice" 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 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.

Development

To start your application in the dev profile, simply run:

./gradlew bootRepackage -Pdev buildDocker # this will build all required containers

docker-compose -f src/main/docker/app.yml up -d

The application will listen on 9080 for requests

For further instructions on how to develop with JHipster, have a look at Using JHipster in development.

Building for production

To optimize the conferencemanager 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.

Testing

To launch your application's tests, run:

./gradlew test

Other tests

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.

Using Docker to simplify development (optional)

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 (yo jhipster:docker-compose), which is able to generate docker configurations for one or several JHipster applications.

Continuous Integration (optional)

To set up a CI environment, consult the Setting up Continuous Integration page.