MM

Post: nginx

2022-04-14T00:00:00+00:00

aws npm install 시 ec2.micro 뻗어버리는 현상

 npm cache clean --force => 캐시제거
 npm install --verbose => 현재상황 파악

 여전히 오류 

임시방편으로 스왑 공간 계산후 스왑파일 생성하는 방법

메모리 체크  free -m 

1.    dd 명령을 사용하여 루트 파일 시스템에 스왑 파일을 생성합니다. 명령에서 bs는 블록 크기이고 count는 블록 수입니다. 스왑 파일의 크기는 dd 명령의 블록 크기 옵션에 블록 수 옵션을 곱한 값입니다. 이러한 값을 조정하여 원하는 스왑 파일 크기를 결정합니다.

지정한 블록 크기는 인스턴스에서 사용 가능한 메모리보다 작아야 합니다. 그렇지 않으면 "memory exhausted" 오류가 발생합니다.

이 예제 dd 명령에서 스왑 파일은 4GB(128MB x 32)입니다.

$ sudo dd if=/dev/zero of=/swapfile bs=128M count=32
2.    스왑 파일의 읽기 및 쓰기 권한을 업데이트합니다.

$ sudo chmod 600 /swapfile
3.    Linux 스왑 영역을 설정합니다.

$ sudo mkswap /swapfile
4.    스왑 공간에 스왑 파일을 추가하여 스왑 파일을 즉시 사용할 수 있도록 합니다.

$ sudo swapon /swapfile
5.    프로시저가 성공적인지 확인합니다.

$ sudo swapon -s
6.    /etc/fstab 파일을 편집하여 부팅 시 스왑 파일을 시작합니다.

편집기에서 파일을 엽니다.

$ sudo vi /etc/fstab
파일 끝에 다음 줄을 새로 추가하고 파일을 저장한 다음 종료합니다.

/swapfile swap swap defaults 0 0

Post: nginx

2022-04-13T00:00:00+00:00

nginx config

conf.d
server {
        listen 0.0.0.0:80;
        server_name _;
        location / {
                root /usr/share/nginx/html/images;
        }
 
        location /api {
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header Host $http_host;
                proxy_set_header X-NginX-Proxy true;

                proxy_pass http://localhost:3100;
                proxy_redirect off;
        }
        location /profile {
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header Host $http_host;
                proxy_set_header X-NginX-Proxy true;

                proxy_pass http://localhost:3000;
                proxy_redirect off;
        }
        location /images {
                alias /usr/share/nginx/html/images/;
        }

}

# For more information on configuration, see:
#   * Official English Documentation: http://nginx.org/en/docs/
#   * Official Russian Documentation: http://nginx.org/ru/docs/

user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;

# Load dynamic modules. See /usr/share/doc/nginx/README.dynamic.
include /usr/share/nginx/modules/*.conf;

events {
    worker_connections 1024;
}

http {
    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;

    sendfile            on;
    tcp_nopush          on;
    tcp_nodelay         on;
    keepalive_timeout   65;
    types_hash_max_size 4096;

    include             /etc/nginx/mime.types;
    default_type        application/octet-stream;

    # Load modular configuration files from the /etc/nginx/conf.d directory.
    # See http://nginx.org/en/docs/ngx_core_module.html#include
    # for more information.
  
    
    proxy_cache_path /var/cache/nginx/images/ levels=1:2 keys_zone=cache_zone:40m inactive=7d max_size=100m;
    proxy_temp_path /var/cache/nginx/temp/;
    proxy_cache_key "$scheme$request_method$host$request_uri";
 
    include /etc/nginx/conf.d/*.conf;
   
     server {
        listen       80;
        listen       [::]:80;
        server_name  _;
        # root         /usr/share/nginx/html;
        # root /usr/share/nginx/html/images;             
        access_log on;
        # Load configuration files for the default server block.
        include /etc/nginx/default.d/*.conf;

        error_page 404 /404.html;
        location = /404.html {
        }

        error_page 500 502 503 504 /50x.html;
        location = /50x.html {
        }
    }

# Settings for a TLS enabled server.
#
#    server {
#        listen       443 ssl http2;
#        listen       [::]:443 ssl http2;
#        server_name  _;
#        root         /usr/share/nginx/html;
#
#        ssl_certificate "/etc/pki/nginx/server.crt";
#        ssl_certificate_key "/etc/pki/nginx/private/server.key";
#        ssl_session_cache shared:SSL:1m;
#        ssl_session_timeout  10m;
#        ssl_ciphers PROFILE=SYSTEM;
#        ssl_prefer_server_ciphers on;
#
#        # Load configuration files for the default server block.
#        include /etc/nginx/default.d/*.conf;
#
#        error_page 404 /404.html;
#            location = /40x.html {
#        }
#
#        error_page 500 502 503 504 /50x.html;
#            location = /50x.html {
#        }
#    }

}

Post: Docker3 -docker swarm

2022-03-24T00:00:00+00:00

docker-swarm

  * docker info 
  - looking for swram in docker info list
  
  inactive 면

  docker swram init
  - 이때 토큰이 발생한다 join token 다른(떨어진 물리적으로) 인스턴스에 설치하여 합류가능
  docker swarm join --token < contents >
   -- 합류한 인스턴스 역할 변경
   docker node update --role manager or worker node 2
  - 토큰 발생시키기
  docker swarm join-token manager or worker
  -- 목록조회 
  docker node ls

  
  * create service
  docker create service <image> <ping> port
  docker service ps <serviceId>
  - 서비스확인
  docker service ps 
  - 클러스터 3개로 돌리기 (docker container rm을 하여도 자동으로 다시 돌린다.)
  docker service update <serviceId> --replicas 3
  - 도커 네트워크 생성
  docker network create --driver overlay mydrupal
  - 도커 서비스 생성 sql network 환경 이미지이름
  docker service create --name psql --network mydrupal -e POSTGRES_PASSWORD=123 postgres
  - example 
  docker service create --name drupal --network mydrupal -p 80:80 drupal
  docker service create --name search --replicas 3 -p 9200:9200 elasticsearch:2
  

linux

2022-03-23T00:00:00+00:00

linux 유용한 명령어 모음

  * shell 확인
   - echo $SHELL  
  * alias 지정
   - alias  #list
   - ~/.bashrc #vi/vim  후 source
   - alias dd=''  

Post: Docker3 -docker compose

2022-03-23T00:00:00+00:00

docker-compose

 * configure relationships between containers
 * save our docker container run settings in easy to read file
 * create one-liner developer environment startups
 * comprised of 2 separate but related things
 * using yaml 
  - containers
  - networks
  - volumes
 *

docker-compose.yaml

  version: '3.1'  # if no version is specified then v1 is assumed. Recommend v2 minimum

  services:  # containers. same as docker run
    servicename: # a friendly name. this is also DNS name inside network
      image: # Optional if you use build:
      command: # Optional, replace the default CMD specified by the image
      environment: # Optional, same as -e in docker run
      volumes: # Optional, same as -v in docker run
    servicename2:

  volumes: # Optional, same as docker volume create

  networks: # Optional, same as docker network create

  ////////////// example
  version: '2'

  # same as 
  # docker run -p 80:4000 -v $(pwd):/site bretfisher/jekyll-serve

  services:
    jekyll:
      image: bretfisher/jekyll-serve
      volumes:
        - .:/site
      ports:
        - '80:4000'

  ////////////// example2
  version: '2'
  services:

    wordpress:
      image: wordpress
      ports:
        - 8080:80
      environment:
        WORDPRESS_DB_HOST: mysql
        WORDPRESS_DB_NAME: wordpress
        WORDPRESS_DB_USER: example
        WORDPRESS_DB_PASSWORD: examplePW
      volumes:
        - ./wordpress-data:/var/www/html

    mysql:
      # we sue mariadb here for arm support
      # mariadb is a fork of MySQL that's often faster and better multi-platform
      image: mariadb
      environment:
        MYSQL_ROOT_PASSWORD: examplerootPW
        MYSQL_DATABASE: wordpress
        MYSQL_USER: example
        MYSQL_PASSWORD: examplePW
      volumes:
        - mysql-data:/var/lib/mysql

  volumes:
    mysql-data:

  ////////////// example3
  version: '3'
# NOTE: This example only works on x86_64 (amd64)
# Percona doesn't yet publish arm64 (Apple Silicon M1) or arm/v7 (Raspberry Pi 32-bit) images

services:
  ghost:
    image: ghost // webserver
    ports:
      - "80:2368"
    environment:
      - URL=http://localhost
      - NODE_ENV=production
      - MYSQL_HOST=mysql-primary
      - MYSQL_PASSWORD=mypass
      - MYSQL_DATABASE=ghost
    volumes:
      - ./config.js:/var/lib/ghost/config.js
    depends_on:
      - mysql-primary
      - mysql-secondary
  proxysql:
    # image only works on x86_64 (amd64)
    image: percona/proxysql
    environment:
      - CLUSTER_NAME=mycluster
      - CLUSTER_JOIN=mysql-primary,mysql-secondary
      - MYSQL_ROOT_PASSWORD=mypass

      - MYSQL_PROXY_USER=proxyuser
      - MYSQL_PROXY_PASSWORD=s3cret
  mysql-primary:
    # image only works on x86_64 (amd64)
    image: percona/percona-xtradb-cluster:5.7
    environment:
      - CLUSTER_NAME=mycluster
      - MYSQL_ROOT_PASSWORD=mypass
      - MYSQL_DATABASE=ghost
      - MYSQL_PROXY_USER=proxyuser
      - MYSQL_PROXY_PASSWORD=s3cret
  mysql-secondary:
    # image only works on x86_64 (amd64)
    image: percona/percona-xtradb-cluster:5.7
    environment:
      - CLUSTER_NAME=mycluster
      - MYSQL_ROOT_PASSWORD=mypass

      - CLUSTER_JOIN=mysql-primary
      - MYSQL_PROXY_USER=proxyuser
      - MYSQL_PROXY_PASSWORD=s3cret
    depends_on:
      - mysql-primary

docker compose cli

* most common use
- docker-compose up # setup volumes/networks and start all containers
- docker-compose donw # stop all containers and remove container/volume/network

  * example 
  version: '3'

  services:
    proxy:
      image: nginx:1.13 # this will use the latest version of 1.13.x
      ports:
        - '80:80' # expose 80 on host and sent to 80 in container
      volumes:
        - ./nginx.conf:/etc/nginx/conf.d/default.conf:ro #ro is readonly
    web:
      image: httpd  # this will use httpd:latest
  -----
  here is example 

Post: Docker2

2022-03-22T00:00:00+00:00

docker-doc

docker image command

// 도커 이미지 정보 
docker image inspect <imageName>


// 도커 이미지 태그정보 변경
docker image tag <imageName> <wantedName like dole/nginx>

// 태그정보 변경된 이름으로 푸쉬
docker image push <targetName>

// 도커 로그인/로그아웃
docker login/logout

// 로그인 정보확인
cat .docker/config.json

docker build dockerfile

// 도커파일 빌드

docker image build -t customnginx .
-> docker image build -target <wantedName> <. = currentfolder>

About dockerfile

  FROM : Docker Base Image (기반이 되는 이미지, <이미지 이름>:<태그> 형식으로 설정)
  MAINTAINER : 메인테이너 정보 (작성자 정보)
  RUN : Shell Script 또는 명령을 실행
  CMD : 컨테이너가 실행되었을 때 명령이 실행
  LABEL : 라벨 작성 (docker inspect 명령으로 label 확인할 수 있습니다.)
  EXPOSE : 호스트와 연결할 포트 번호를 설정한다.
  ENV : 환경변수 설정
  ADD : 파일 / 디렉터리 추가
  COPY : 파일 복사
  ENTRYPOINT : 컨테이너가 시작되었을 때 스크립트 실행
  VOLUME : 볼륨 마운트
  USER : 명령 실행할 사용자 권한 지정
  WORKDIR : "RUN", "CMD", "ENTRYPOINT" 명령이 실행될 작업 디렉터리
  ARG : Dockerfile 내부 변수
  ONBUILD : 다른 이미지의 Base Image로 쓰이는 경우 실행될 명령 수행
  SHELL : Default Shell 지정

dockerfile run

# Dockerfile
  FROM node:6-alpine
  EXPOSE xxxx
  RUN apk add --update tini
  RUN mkdir -p /usr/src/app 
  WORKDIR /usr/src/app
  COPY package.json package.json
  RUN npm install && npm cache clean --force
  COPY . .
  CMD [ "tini", "--", "node", "./bin/www"]


docker build -t mynode .
docker container run --rm -p 80:3000 mynode

도커에서 포트 의미 => 내포트:컨테이너포트

prune

 -- 사용하지않는 이미지 삭제
 docker image prune

 -- 사용하지 않는 컨테이너 삭제
 docker container prune

 -- 사용하지 않는 볼륨 삭제
 docker container prune
 
 -- 사용하지 않는 네트워크 삭제
 docker container prune

 -- 사용하지 않는 docker object삭제
 docker system prune
 

도커 볼륨 확인

-- 도커에서 mysql 등 persistent data 등은 볼륨에서 확인할 수 있는데
docker contianer inspect <container> 시 마운트에서 정보를 확인 할 수 있다.
        "Mounts": [
            {
                "Type": "volume",
                "Name": "a524a4a94f434b7f9e2edc355aff1941b261bd782e525dbb7c08751d9040b461",
                "Source": "/var/lib/docker/volumes/a524a4a94f434b7f9e2edc355aff1941b261bd782e525dbb7c08751d9040b461/_data",
                "Destination": "/var/lib/mysql",
                "Driver": "local",
                "Mode": "",
                "RW": true,
                "Propagation": ""
            }
        ],

name으로 볼륨확인을 할 수 있는데
내 로컬 볼륨을 확인해보면
docker volume ls => 
docker volume inspect <volume>
컨테이너 실행할때마다 영속성 데이터 볼륨은 생성되는데 정지해도 없어지지 않는다
docker container run -d --name mysql -e MYSQL_ALLOW_EMPTY_PASSWORD=True -v mysql-db:/var/lib/mysql mysql
-v 명령어는 볼륨 지정 및 볼륨 네이밍을 할 수 있는데 이로 관리하는게 편함

도커 볼륨 생성

docker volume create <options>

bind mounting

* 도커파일에서는 쓰면 안되고 container run 명령어로 써야함
                  ($pwd) or {$pwd}: container path
container run -v /usr/myfolder/directory:/conatinerpath/directory (mac/linux)

도커 이미지 생성한 폴더에서 폴더를 만들거나 파일을 만들면 컨테이너 패스에도 똑같이 나타남

rewriting docker bash 명령어

docker container exec -it <conatiner> bash

Post: Docker1

2022-03-21T00:00:00+00:00

docker-doc

ec2 용량 꽉찻을경우

df -hT #각 볼륨의 파일시스템 용량, 타입 확인

du <dir> #

EBS 콘솔에서 내 볼륨 우클릭 후 수정해서 크기를 8에서 16으로 수정함.
lsblk 명령어로 인스턴스에 연결된 블록디바이스를 확인

sudo growpart <볼륨> <파티션번호>

sudo resize2fs <파티션>

권한이없을경우 권한부여
sudo chmod 666 /var/run/docker.sock

권한부여후 sudo usermod -a -G docker ec2-user

docker info

도커 아마존리눅스설치

  sudo yum update -y
  sudo amazon-linux-extras install docker
  sudo service docker start
  sudo usermod -a -G docker ec2-user
  docker info

도커 이미지생성

  touch Dockerfile
  
  RUN apt-get update && \
 apt-get -y install apache2
  
  RUN echo 'Hello World!' > /var/www/html/index.html
  
  RUN echo '. /etc/apache2/envvars' > /root/run_apache.sh && \
 echo 'mkdir -p /var/run/apache2' >> /root/run_apache.sh && \
 echo 'mkdir -p /var/lock/apache2' >> /root/run_apache.sh && \ 
 echo '/usr/sbin/apache2 -D FOREGROUND' >> /root/run_apache.sh && \ 
 chmod 755 /root/run_apache.sh

EXPOSE 80

CMD /root/run_apache.sh
  
  dockerfile 에서 빌드
  docker build -t hello-world .
  
  이미지확인
  docker images --filter reference=hello-world
  
  docker run -t -i -p 80:80 hello-world
  
  docker-machine ip ~machine-name~
  
  # 자동시작도커
  sudo chkconfig docker on
  # 깃설치 반드시
  sudo yum install -y git 
  # 재부팅
  sudo reboot
  
  # docker compose install
  
Copy the appropriate docker-compose binary from GitHub:

sudo curl -L https://github.com/docker/compose/releases/download/1.22.0/docker-compose-$(uname -s)-$(uname -m) -o /usr/local/bin/docker-compose

NOTE: to get the latest version (thanks @spodnet): sudo curl -L https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m) -o /usr/local/bin/docker-compose

Fix permissions after download:

sudo chmod +x /usr/local/bin/docker-compose

Verify success:

docker-compose version

# 도커 이미지 받아서 해당 포트에 프로세스 돌림 (–detach 백그라운드 / 없으면 바로 )

  --detach 백그라운드 / 없으면 바로 
  --name 이름 설정
  docker container run --publish <port> <option> <image>
  docker container run --publish 8022:80 --detach nginx

# 도커 컨테이너 리스트

  docker container ls

# 도커 중지

  docker container stop <container id>

# 도커 로그

  name = 이미지 이름
  docker container logs <name>

# 프로세스에 올려진 도커 컨테이너 확인

  name = 이미지 이름
  docker container top <name>

# 도커 리스트에서 이미지 삭제

  running image는 삭제할수 없음
  -f 명령어 강제 종료
  docker container rm -f <container id>

# docker container run 동작원리

로컬 이미지를 찾는다
도커허브에서 이미지 리모트를 한다
최신버전을 다운로드 받는다. (엔진엑스 최신버전)
컨테이너를만들고 시작함
가상 ip를 부여하고 docker engine을 올려둠
포트 번호에 할당
image dockerfile 에있는 cmd실행

# 리눅스 프로세스 리스트

  포트확인
  netstat -tnlp
  프로세스 확인
  ps aux

# docker container inspect - 컨테이너 설정 확인 # docker container stats - 컨테이너 성능 확인

# docker container exec bash에서 ps -aux가 안먹히는경우

   apt-get update && apt-get install procps

# docker container localshot ip inspect 로 확인하는방법

  docker container inspect --format '' webhost

# docker container network 사용리스트

  docker network ls
  docker network inspect bridge

# docker 버추얼 네트워크 변경

  docker network ls 
  => list id
  docker container ls
  => list id 
  docker network connect <networkId> <containerId>
  
  -->docker container inspect <containerId>

# docker 핑 체크

  docker container exec -it <containerName> bash 
  apt-get update && apt-get install -y iputils-ping

Xcode12frameworkdnotfound

2021-04-29T00:00:00+00:00

title: “Framework Not Found with xcode 12 openssl etc” date: 2021-04-29 categories:

blog tags:
ios
react-native

To do that, navigate to Build Settings of your project and add Any iOS Simulator SDK with value arm64 inside Excluded Architecture.

일반적으로 user-define 설정을 따르지 않는경우 arm64를 excluded architecture.에 any ios simulator에 넣는다 넣고 cleanbuild 후 에뮬레이터를 돌린다.

XCConfig 파일을 사용할 경우에는

EXCLUDED_ARCHS[sdk=iphonesimulator*] = arm64

Pod project에

s.pod_target_xcconfig = { 'EXCLUDED_ARCHS[sdk=iphonesimulator*]' => 'arm64' }
s.user_target_xcconfig = { 'EXCLUDED_ARCHS[sdk=iphonesimulator*]' => 'arm64' }

한후 pod install

post_install do |installer|
  installer.pods_project.build_configurations.each do |config|
    config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
  end
end

참고 https://stackoverflow.com/questions/63607158/xcode-12-building-for-ios-simulator-but-linking-in-object-file-built-for-ios?page=1&tab=votes#tab-top

First Post

2021-03-02T00:00:00+00:00

title: “Redux selector 관련” date: 2021-03-02 categories:

blog tags:
redux
selector

const [friends, frends2] = useSelector(state => [state.friend.friends, state.friend.friends2], shallowEqual)

friends, friends2의 레퍼런스만 비교하는 것이 아니고 각각을 비교하기 때문에 friends 만 렌더링이 된다.

매번 shallowEqual을 쓰는 것은 불편하여 커스텀 훅을 만들어서 사용하길 권장

function useMyselector(selector) {
  return useSelector(selector, shallowEqual);
}

const [value, value2] = useMyselector(state => [state.value1, state.value2]);

이렇게 커스텀 훅을 사용할때는 모든 값을 비교하기 때문에 배열로 반환해주는 것이 좋다.

const [value4] = useMyselector(state => [state.value4])

상태값을 여러개 사용하는 또다른 방법은 reselect를 이용하는 방법이 있다.

import { createSelector } from 'reselect'

const getFriends = state => state.friend.friends;
const getAgeLimit = state => state.friend.ageLimit;
const getAgeShowLimit = state => state.friend.showLimit;
export const getFriendWithAgeLimit  = createSelector(
  [ getFriends, getAgeLimit ],
  (friends, ageLimit) => friends.filter(item => item.age <= ageLimit),
)

export const getFriendWithAgeShowLimit  = createSelector(
  [ getFriendWithAgeLimit , geShowtAgeLimit ],
  ( friendsWithAgeLimit, showLimit ) => friendsWithAgeLimit.slice(0, showLimit),
)

### 렌더링 부분

const [ 
  ageLimit,
  showLimit,
  friendsWithAgeLimit,
  friendsWithAgeShowLimit
] = useSelector(
  state => [
    getAgeLimit(state),
    getShowLimit(state),
    getFriendsWithAgeLimit(state),
    getFriendsWithAgeShowLimit(state)
  ],
  shallowEqual,
)

이렇게 작성을하면 값으로 넘어오는 변수들이 변경되었을때만 실행을 하기때문에 메모이제이션 기능을 쓴다.

jpa h2 connection

2019-04-18T19:34:30+00:00

Are you using >=2.3.0 Release of Spring Boot? You would need to configure this in application.properties.

spring.datasource.url=jdbc:h2:mem:testdb

Why is this needed? With the latest versions of Spring Boot (2.3+), the H2 database name is randomly generated each time you restart the server. We do NOT want that. We want a constant URL.

H2 console available at '/h2-console'. Database available at 'jdbc:h2:mem:dd222195-7e0b-4dc0-ae4c-7f53e5ea7ceb'

Make sure you are using jdbc:h2:mem:testdb as the database URL in H2 Console as shown in the image below.

In the browser, change the database url to jdbc:h2:mem:testdb (Shown in the screen below).

Do you have H2 dependency in pom.xml? Try removing <scope>runtime</scope> and see if it makes a difference.

<dependency>
	<groupId>com.h2database</groupId>
	<artifactId>h2</artifactId>
</dependency>

Check if H2 Console is enabled in application.properties

spring.h2.console.enabled=true

Delete your maven local repository (content of .m2 folder) and rebuild the project. (You are right. This looks silly. But do not skip it. I’ve seen many problems caused by dependency caches!)

Tables are not created

Are you using Spring Boot >=2.5.0 Release?

Are you using >=2.5.0 Release of Spring Boot? You would need to configure this in application.properties.

spring.jpa.defer-datasource-initialization=true

OR you can use schema.sql instead of data.sql

Why is this needed? https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.5.0-M3-Release-Notes#hibernate-and-datasql => By default, data.sql scripts are now run before Hibernate is initialized. This aligns the behaviour of basic script-based initialization with that of Flyway and Liquibase. If you want to use data.sql to populate a schema created by Hibernate, set spring.jpa.defer-datasource-initialization to true. While mixing database initialization technologies is not recommended, this will also allow you to use a schema.sql script to build upon a Hibernate-created schema before it’s populated via data.sql

No 1 : Are you using Spring Boot >=2.3.0 Release?

Configure this in application.properties

spring.datasource.url=jdbc:h2:mem:testdb
spring.data.jpa.repositories.bootstrap-mode=default

You should see this in the log

H2 console available at '/h2-console'. Database available at 'jdbc:h2:mem:testdb'

Why do we need to configure bootstrap-mode? Details here - https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.3-Release-Notes#bootstrapmode-for-jpa-repositories

No 2 : Make sure you have the right annotations!

Make sure that the Entities have @Entity annotation and the Repository class has @Repository annotation

No 3 : Make sure you do NOT have schema.sql

Delete schema.sql if you have created one.

If schema.sql file exist, tables are NOT created.

No 4 : Make sure your component is picked up by Component Scan

Spring Boot does a component scan in the package and sub-packages where your @SpringBootApplication is defined.

Why is this important? If your entity class or the repository class is NOT under the package of your @SpringBootApplication class, it will NOT be picked up by component scan.

RECOMMENDED OPTION - Option 1 : Move the component under component scan

Simplest way to fix this is to identify the packages of the SpringBootApplication class and move all the components into that package or sub-packages of it.

Option 2 : Add component and entity scan for the packages containing the components

@SpringBootApplication(scanBasePackages= {"com.project.currency.*"})
@EntityScan(basePackages = {"com.project.currency.model"})
@EnableJpaRepositories(basePackages = {"com.project.currency.repository"})

Learn more about component scan:

https://github.com/in28minutes/in28minutes-initiatives/tree/master/The-in28Minutes-TroubleshootingGuide-And-FAQ#q—what-is-the-need-for-a-component-scan

2.3.0 Course Update

With the latest versions of Spring Boot (2.3+), the H2 database name is randomly generated each time you restart the server.

You can find the database name and URL from the console log.

If you face any problems:

Spring Boot 2.3.1 Upgrade - Changes

https://github.com/in28minutes/jpa-with-hibernate/commit/1f30e868ccd2eb7e69cdb989bc990cd00cc82168

JUnit 5 Upgrade - Changes

https://github.com/in28minutes/jpa-with-hibernate/commit/0ae2007c8e08420e6d5ab2a86499274c7c60c8ae

MM

Post: nginx

aws npm install 시 ec2.micro 뻗어버리는 현상

임시방편으로 스왑 공간 계산후 스왑파일 생성하는 방법

Post: nginx

nginx config

Post: Docker3 -docker swarm

docker-swarm

linux

linux 유용한 명령어 모음

Post: Docker3 -docker compose

docker-compose

docker-compose.yaml

docker compose cli

Post: Docker2

docker-doc

docker image command

docker build dockerfile

About dockerfile

dockerfile run

도커에서 포트 의미 => 내포트:컨테이너포트

prune

도커 볼륨 확인

도커 볼륨 생성

bind mounting

rewriting docker bash 명령어

Post: Docker1

docker-doc

ec2 용량 꽉찻을경우

도커 아마존리눅스설치

도커 이미지생성

Xcode12frameworkdnotfound

react-native

First Post

selector

jpa h2 connection

Unable to login into H2 Console

Tables are not created

Are you using Spring Boot >=2.5.0 Release?

No 1 : Are you using Spring Boot >=2.3.0 Release?

No 2 : Make sure you have the right annotations!

No 3 : Make sure you do NOT have schema.sql

No 4 : Make sure your component is picked up by Component Scan

RECOMMENDED OPTION - Option 1 : Move the component under component scan

Option 2 : Add component and entity scan for the packages containing the components

2.3.0 Course Update

RECOMMENDED:

If you face any problems: