By default, JHipster will generate Docker Compose files that enable us to run the application completely in the containerized environment, irrespective of the options chosen. For example, in the gateway application that we have generated, the following files are generated by default under src/main/docker:
- sonar.yml: This file creates and starts a SonarQube server
- mysql.yml: This file creates and starts a MySQL database server and creates a user and schema
- jhipster-registry.yml: This file creates and starts a JHipster Registry service
- app.yml: This is the main file that creates and starts the application along with services such as JHipster registry and the database
In addition to this, JHipster also creates a Dockerfile, which helps you to containerize the application alone.
Then we can see a folder called central-server-config. This will be used as a central configuration server for the JHipster Registry.
When the registry and the application are running in Docker, it uses application.yml from the docker-config folder as the central configuration server.
On the other hand, when running only the registry in Docker mode, the application, not in Docker, will use application.yml from the localhost-config folder. The key difference is that the URL defining the Eureka client varies.
Let's see the Docker files that have been generated.