installation Issues

1. sudo chown -R whoami ~/.npm

How to operate this

1. wsl port forwarding
2. db and redis up on docker by 'npm run docker:db:up' and 'npm run docker:redis:up'
3. backend up by 'npm run backend:start' ( on root authority or "sudo chown -R $whoami ~/.npm)
4. 'npm start' for webapps with Browsersync. This is going to operate on WDS(Webpack Dev Server)
5. go to mobile directory and start react native app,'npm run start3'='EXPO_DEVTOOLS_LISTEN_ADDRESS=0.0.0.0 REACT_NATIVE_PACKAGER_HOSTNAME=192.168.0.13 expo start'
6. change url on browser from 0.0.0.0:19002 to hostIP:19002

Operating Issues

1. expo devtool 접근문제
   문제 : expo devtool 접근이 안됨 (19002 포트)
   해결: 2가지 처리 필요
   a. expo devtools 의 접근 IP를 모든 IP로 변경 (0.0.0.0) ( EXPO_DEVTOOLS_LISTEN_ADDRESS=0.0.0.0)
   b. websocket 접근 불가 문제는 브라우저 창에 호스트IP 를 직접 넣어서 접근함 ( 192.168.0.36:19002 )
   link : https://blog.naver.com/kjamjalee/222307200425
   

2. Webapps Hot Reload 문제
   문제 : localhost:8080 로도 Webapp 접근 가능하나, Hot Reload 가 안되어서 서버 재가동 필요
   해결 : Webpack Dev Server 위에서 Webapps 이 작동되게 변경
   a. 'npm start' or 'npm run webapp:dev'
   b. package.json 에서 script 설정 파일에 web-dev-server 설정 값 참고
   

3. Mobile side(react-native) access error
   문제 : mobile 쪽에서 백엔드 접속 안됨
   해결 : CORS 정책 문제로, 백엔드쪽에서 설정 변경 필요
   a. fix Cors problems, add http://localhost:19006 at cors configuration on backend.
   

org

This application was generated using JHipster 7.0.1, you can find documentation and help at https://www.jhipster.tech/documentation-archive/v7.0.1.

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.

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.

npm install

We use npm scripts and Webpack as our build system.

If you are using redis as a cache, you will have to launch a cache server. To start your cache server, run:

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

The cache can also be turned off by adding to the application yaml:

spring:
    cache:
        type: none

See here for details.

WARNING: If you using second level hibernate cache and disabling the spring cache, you have to disable the second level hibernate cache as well since they are using the same CacheManager.

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
npm start

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

The npm run command will list all of the scripts available to run for this project.

PWA Support

JHipster ships with PWA (Progressive Web App) support, and it's turned off by default. One of the main components of a PWA is a service worker.

The service worker initialization code is commented out by default. To enable it, uncomment the following code in src/main/webapp/index.html:

<script>
  if ('serviceWorker' in navigator) {
    navigator.serviceWorker.register('./service-worker.js').then(function () {
      console.log('Service Worker Registered');
    });
  }
</script>

Note: Workbox powers JHipster's service worker. It dynamically generates the service-worker.js file.

Managing dependencies

For example, to add Leaflet library as a runtime dependency of your application, you would run following command:

npm install --save --save-exact leaflet

To benefit from TypeScript type definitions from DefinitelyTyped repository in development, you would run following command:

npm install --save-dev --save-exact @types/leaflet

Then you would import the JS and CSS files specified in library's installation instructions so that Webpack knows about them: Note: There are still a few other things remaining to do for Leaflet that we won't detail here.

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 org application for production, run:

./mvnw -Pprod clean verify

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/*.jar

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

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:

./mvnw -Pprod,war clean verify

Testing

To launch your application's tests, run:

./mvnw verify

Client tests

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

npm test

For more information, refer to the Running tests page.

Code quality

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 authentication 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 maven plugin.

Then, run a Sonar analysis:

./mvnw -Pprod clean verify sonar:sonar

If you need to re-run the Sonar phase, please be sure to specify at least the initialize phase since Sonar properties are loaded from the sonar-project.properties file.

./mvnw initialize sonar:sonar

For more information, refer to the Code quality 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 -Pprod verify jib:dockerBuild

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.

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.