java-tutorials/jhipster/jhipster-microservice/gateway-app
amit2103 f2128ad054 Bael 5249 cleanup (#4108)
* Added parent module on poms that have no parent defined

* Removed dependency reduced pom from undertow module

* [BAEL-5249] - 21.02 - pom cleanup - formatted pom.xml
2018-04-26 14:37:47 +02:00
..
.jhipster BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
.mvn/wrapper BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
gulp BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
src fix test names (#1865) 2017-05-16 11:03:40 -05:00
.bowerrc BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
.editorconfig BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
.eslintignore BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
.eslintrc.json BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
.gitattributes BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
.gitignore BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
.yo-rc.json BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
README.md BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
bower.json BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
gulpfile.js BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
mvnw BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
mvnw.cmd BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
package.json BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00
pom.xml Bael 5249 cleanup (#4108) 2018-04-26 14:37:47 +02:00
yarn.lock BAEL-521 (#1799) 2017-05-07 19:00:32 +02:00

README.md

gateway

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

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

Before you can build this project, you must install and configure the following dependencies on your machine:

  1. Node.js: We use Node to run a development web server and build the project. Depending on your system, you can install Node either from source or as a pre-packaged bundle.
  2. Yarn: We use Yarn to manage Node dependencies. Depending on your system, you can install Yarn either from source or as a pre-packaged bundle.

After installing Node, you should be able to run the following command to install development tools. You will only need to run this command when dependencies change in package.json.

yarn install

We use Gulp as our build system. Install the Gulp command-line tool globally with:

yarn global add gulp-cli

Run the following commands in two separate terminals to create a blissful development experience where your browser auto-refreshes when files change on your hard drive.

./mvnw
gulp

Bower is used to manage CSS and JavaScript dependencies used in this application. You can upgrade dependencies by specifying a newer version in bower.json. You can also run bower update and bower install to manage dependencies. Add the -h flag on any command to see how you can use it. For example, bower update -h.

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

Building for production

To optimize the gateway application for production, run:

./mvnw -Pprod clean package

This will concatenate and minify the client CSS and JavaScript files. It will also modify index.html so it references these new files. To ensure everything worked, run:

java -jar target/*.war

Then navigate to http://localhost:8080 in your browser.

Refer to Using JHipster in production for more details.

Testing

To launch your application's tests, run:

./mvnw clean test

Client tests

Unit tests are run by Karma and written with Jasmine. They're located in src/test/javascript/ and can be run with:

gulp test

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 mysql database in a docker container, run:

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

To stop it and remove the container, run:

docker-compose -f src/main/docker/mysql.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:

./mvnw package -Pprod docker:build

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 configure CI for your project, run the ci-cd sub-generator (yo 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.