Files

T

$NAS\NASPC$ NAS\NASPC 109c09d2a3 update backgrounnd video for header.html

2026-06-05 09:49:06 +07:00

9.6 KiB

Raw Blame History

sisvietnamvn

This application was generated using JHipster 9.1.0, you can find documentation and help at https://www.jhipster.tech/documentation-archive/v9.1.0.

Project Structure

Node is required for generation and recommended for development. package.json is always generated for a better development experience with prettier, commit hooks, scripts and so on.

In the project root, JHipster generates configuration files for tools like git, prettier, eslint, husky, and others that are well known and you can find references in the web.

/src/* structure follows default Java structure.

.yo-rc.json - Yeoman configuration file JHipster configuration is stored in this file at generator-jhipster key. You may find generator-jhipster-* for specific blueprints configuration.
.yo-resolve (optional) - Yeoman conflict resolver Allows to use a specific action when conflicts are found skipping prompts for files that matches a pattern. Each line should match [pattern] [action] with pattern been a Minimatch pattern and action been one of skip (default if omitted) or force. Lines starting with # are considered comments and are ignored.
.jhipster/*.json - JHipster entity configuration files
/src/main/docker - Docker configurations for the application and services that the application depends on

Database Configuration

Development Database (H2 Console)

Profile: dev
Database Type: H2 (File-based, embedded)
JDBC URL: jdbc:h2:file:./build/h2db/db/sisvietnamvn
Username: sisvietnamvn
Password: (leave blank)
Console Access: http://localhost:8080/h2-console (requires app running in dev profile)
Config File: application-dev.yml

Production Database

Profile: prod
Database Type: Oracle Database
JDBC URL: jdbc:oracle:thin:@localhost:1521:xe
Username: sisvietnamvn
Config File: application-prod.yml

Schema Management

Tool: Liquibase
Changelog Folder: src/main/resources/config/liquibase/

Development

To start your application in the dev profile, run:

./gradlew

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

Building for production

Packaging as jar

To build the final jar and optimize the sisvietnamvn application for production, run:

./gradlew -Pprod clean bootJar

To ensure everything worked, run:

java -jar build/libs/*.jar

Refer to [Using JHipster in production][] for more details.

Packaging as war

To package your application as a war in order to deploy it to an application server, run:

./gradlew -Pprod -Pwar clean bootWar

JHipster Control Center

JHipster Control Center can help you manage and control your application(s). You can start a local control center server (accessible on http://localhost:7419) with:

docker compose -f src/main/docker/jhipster-control-center.yml up

Testing

Spring Boot tests

To launch your application's tests, run:

./gradlew test integrationTest jacocoTestReport

Others

Code quality using Sonar

Sonar is used to analyse code quality. You can start a local Sonar server (accessible on http://localhost:9001) with:

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

Note: we have turned off forced authentication redirect for UI in src/main/docker/sonar.yml for out of the box experience while trying out SonarQube, for real use cases turn it back on.

You can run a Sonar analysis with using the sonar-scanner or by using the gradle plugin.

Then, run a Sonar analysis:

./gradlew -Pprod clean check jacocoTestReport sonarqube -Dsonar.login=admin -Dsonar.password=admin

Additionally, Instead of passing sonar.password and sonar.login as CLI arguments, these parameters can be configured from sonar-project.properties as shown below:

sonar.login=admin
sonar.password=admin

For more information, refer to the [Code quality page][].

Docker Compose support

JHipster generates a number of Docker Compose configuration files in the src/main/docker/ folder to launch required third party services.

For example, to start required services in Docker containers, run:

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

To stop and remove the containers, run:

docker compose -f src/main/docker/services.yml down

Spring Docker Compose Integration is enabled by default. It's possible to disable it in application.yml:

spring:
  ...
  docker:
    compose:
      enabled: false

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:

npm run java:docker

Or build an arm64 Docker image when using an arm64 processor OS, i.e., Apple Silicon chips (M*), running:

npm run java:docker:arm64

Then run:

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

For more information refer to 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.

Continuous Integration (optional)

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.

References

#Structure

Using NGINX (via aaPanel) with Tomcat is a very common and recommended setup. In this architecture, NGINX acts as a Reverse Proxy. It handles incoming internet traffic (ports 80 and 443 for SSL) and forwards the requests to your Tomcat application running in the background (usually on port 8080).

Here is the step-by-step guide to setting this up in aaPanel:

Step 1: Start your Tomcat/Spring Boot App Make sure your application is running. By default, your project seems to run on port 8080.

If using embedded Tomcat: Run your .jar file in the background (e.g., nohup java -jar your-app.jar --spring.profiles.active=prod &). If using standalone Tomcat: Ensure Tomcat is started and the app is deployed. Step 2: Configure the Website in aaPanel Log in to your aaPanel dashboard. Go to the Website menu on the left sidebar. Click Add site (if you haven't already). Enter your domain name (e.g., sisvietnam.vn). For PHP version, select Static (since Java handles the backend, you don't need PHP). Click Submit to create the site. Step 3: Set up the Reverse Proxy In the Website list, click on the Settings button for your newly created domain. In the settings window, click on the Reverse proxy tab on the left. Click Add reverse proxy and fill in the details: Proxy name: Give it any name (e.g., TomcatProxy). Target URL: Enter http://127.0.0.1:8080 (Change 8080 if your app is running on a different port). Sent Domain: Leave it as $host (the default). Click Submit. Step 4: Configure Spring Boot to Trust the Proxy (Crucial) Because NGINX sits in front of your app, Tomcat will think all requests are coming from 127.0.0.1 instead of the user's real IP, and it might get confused about http vs https (which breaks redirects and security).

To fix this, you need to tell your Spring Boot app to read the headers forwarded by NGINX. Open your src/main/resources/config/application-prod.yml (or application.yml) and add:

yaml server: forward-headers-strategy: framework (Note: JHipster usually configures this automatically for the prod profile, but it is good to double-check).

Summary of How it Works Now: A user visits https://your-domain.com. NGINX (aaPanel) receives the request on port 443. NGINX forwards the request to http://127.0.0.1:8080. Tomcat (Java) processes the request and sends the HTML/JSON back to NGINX. NGINX sends the response back to the user. You can also use aaPanel's built-in SSL manager to easily apply Let's Encrypt certificates to your NGINX site, and your Tomcat backend won't need to worry about SSL certificates at all!

9.6 KiB Raw Blame History