-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[20기_최서지] Docker & API 리팩토링 미션 제출합니다. #44
base: choiseoji
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
이번주 과제 너무 고생많으셨습니다😊😊
depends_on: | ||
database: | ||
condition: service_healthy | ||
networks: | ||
- network | ||
env_file: | ||
- .env | ||
|
||
networks: | ||
network: | ||
driver: bridge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
health check 부분과 network 부분 배워갑니다😊
## +) Volume 은 뭘까?? | ||
|
||
docker는 개별적인 가상화 환경인 컨테이너에서 작업을 하여 모든 데이터는 컨테이너 내부에만 존재. | ||
|
||
→ 컨테이너를 삭제하면 컨테이너 내부에서 작업했던 데이터들이 같이 삭제된다. | ||
|
||
→ 데이터는 살리고 싶은데 어떻게 해야 좋을까?? ⇒ **볼륨(volume)** 을 사용하자! | ||
|
||
- 컨테이너 내부의 데이터를 외부로 링크를 걸어주는 기능 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
저는 따로 volume 설정은 안해주었는데 서지님 코드 보고 배워가요😊
No description provided.