-
Notifications
You must be signed in to change notification settings - Fork 0
무중단배포 테스트 #50
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
Merged
무중단배포 테스트 #50
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,9 +6,9 @@ services: | |
| ports: | ||
| - "8080:8080" | ||
| volumes: | ||
| - ./deploy/nginx/nginx.conf:/etc/nginx/nginx.conf:ro | ||
| - ./deploy/nginx/conf.d:/etc/nginx/conf.d:ro | ||
| - ./deploy/runtime:/etc/nginx/runtime | ||
| - ./nginx/nginx.conf:/etc/nginx/nginx.conf:ro | ||
| - ./nginx/conf.d:/etc/nginx/conf.d:ro | ||
| - ./runtime:/etc/nginx/runtime | ||
| networks: | ||
| - vlainter-net | ||
|
|
||
|
|
@@ -17,7 +17,7 @@ services: | |
| container_name: vlainter-app-blue | ||
| restart: always | ||
| env_file: | ||
| - .env | ||
| - ../.env | ||
| environment: | ||
| SERVER_PORT: 18080 | ||
| ports: | ||
|
|
@@ -30,7 +30,7 @@ services: | |
| container_name: vlainter-app-green | ||
| restart: always | ||
| env_file: | ||
| - .env | ||
| - ../.env | ||
|
Comment on lines
32
to
+33
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
| environment: | ||
| SERVER_PORT: 18081 | ||
| ports: | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
../.env와 같이 상위 디렉토리를 참조하는 상대 경로는docker-compose.bluegreen.yml파일이 프로젝트의 전체 디렉토리 구조에 의존하게 만듭니다. 이는 파일 위치 변경 시 예기치 않은 오류를 발생시킬 수 있어 유지보수성을 저해하는 요인이 됩니다.보다 견고한 설계를 위해, 이 compose 파일이 자체 디렉토리 내의 리소스만 참조하도록 하는 것이 좋습니다.
env_file설정을.env로 변경하고, 배포 스크립트(deploy-bluegreen.sh)에서docker-compose를 실행하기 전에 프로젝트 루트의.env파일을deploy디렉토리로 복사하거나 심볼릭 링크를 생성하는 단계를 추가하는 것을 제안합니다.이렇게 하면
docker-compose.bluegreen.yml파일의 독립성이 높아져 설정이 더 명확해지고, 향후 디렉토리 구조 변경에 더 유연하게 대처할 수 있습니다.