-
Notifications
You must be signed in to change notification settings - Fork 8
chore: dev->local, stage->dev 환경명 변경, 배포 방식 변경 #288
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
Conversation
Walkthrough
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Pull Request Overview
This PR renames environment configuration from stage to dev and updates the deployment process to trigger on the develop branch.
- Renamed service and container naming in docker-compose file along with environment variables.
- Updated GitHub Actions workflow to deploy from the develop branch and use the updated docker-compose file.
Reviewed Changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docker-compose.dev.yml | Changed service and container names and updated environment variables from stage to dev. |
| .github/workflows/dev-cd.yml | Adjusted the workflow branch filter and source file for deployment. |
Files not reviewed (1)
- src/main/resources/logback-spring.xml: Language not supported
Comments suppressed due to low confidence (1)
.github/workflows/dev-cd.yml:63
- The deployment target folder name still references 'stage', which may be inconsistent with the dev environment changes. Consider updating it to 'solid-connect-dev' for clarity.
target: "/home/${{ secrets.STAGE_USERNAME }}/solid-connect-stage/"
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.
Actionable comments posted: 0
🔭 Outside diff range comments (1)
.github/workflows/dev-cd.yml (1)
71-76: 🛠️ Refactor suggestion8. 배포 실행 스크립트 파일 참조 오류
- SSH 실행 단계에서docker-compose.stage.yml을 그대로 사용해 새로 복사한docker-compose.dev.yml가 적용되지 않습니다.
- 아래와 같이 수정을 제안합니다:- docker compose -f docker-compose.stage.yml up -d --build + docker compose -f docker-compose.dev.yml up -d --build
🧹 Nitpick comments (1)
src/main/resources/logback-spring.xml (1)
30-34: 1. 프로덕션 및 개발 로그 프로필 변경 적용
-<springProfile>태그가"prod,dev"로 올바르게 업데이트되었습니다.
- 로컬 개발 환경에서도 로그가 필요하다면"local"프로필을 추가하는 것을 검토해 보세요.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
.github/workflows/dev-cd.yml(2 hunks)docker-compose.dev.yml(2 hunks)src/main/resources/logback-spring.xml(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: build
🔇 Additional comments (6)
docker-compose.dev.yml (2)
22-27: 2. 서비스 및 컨테이너 이름 업데이트
- 서비스 이름이solid-connection-dev로, 컨테이너 이름이solid-connection-dev로 적절히 변경되었습니다.
- 이전solid-connection-stage참조가 완전히 제거되었는지 확인 부탁드립니다.
30-31: 3. 환경 변수 ‘dev’ 모드 반영 확인
-SPRING_PROFILES_ACTIVE=dev와ALLOY_ENV=dev로 수정되어 개발 환경이 제대로 반영되었습니다.
- 오타나 누락이 없는지 재검토해 주세요.Also applies to: 45-46
.github/workflows/dev-cd.yml (4)
1-1: 4. 워크플로우 이름 명확화
- 워크플로우명이"[DEV] Build Gradle and Deploy"로 업데이트되어 목적이 명확해졌습니다.
5-5: 5. 브랜치 트리거 환경 전환
- 배포 트리거 브랜치가release에서develop으로 올바르게 변경되었습니다.
62-62: 6. Docker Compose 파일 소스 경로 수정
- 복사 소스가docker-compose.stage.yml에서docker-compose.dev.yml로 업데이트되었습니다.
41-45: 7. 시크릿 및 타깃 디렉토리 네이밍 불일치
- 여전히STAGE_HOST,STAGE_USERNAME,/solid-connect-stage/경로가 사용 중입니다.
- dev 환경 전용 시크릿(DEV_HOST,DEV_USERNAME)과 디렉토리(/solid-connect-dev/)로 변경을 검토해 주세요.
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.
- ${{ secrets.STAGE_USERNAME }}
- target: "/home/${{ secrets.STAGE_USERNAME }}/solid-connect-stage/"
이런 곳에 사용되는 용어도 이번에 한번에 바꾸는게 어떨까요?
혹시나 나중에 헷갈릴 수 있을 것 같아서요 😓
그리고 나중에 DNS의 도메인 이름도 바꾸실건지 궁금해요!
(바꾸신다면 프로메테우스 설정 변경도 잊지 말아주세요~)
| username: ${{ secrets.STAGE_USERNAME }} | ||
| key: ${{ secrets.STAGE_PRIVATE_KEY }} | ||
| source: "./docker-compose.stage.yml" | ||
| source: "./docker-compose.dev.yml" |
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.
이 PR머지되기 전에 docker-compose 파일 이름이 바뀌어야 될 듯 합니다🧐
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.
파일명도 변경을 해두긴 했는데, 머지와 동시에 바꿔지면 문제가 있나요?
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.
아 workflow 파일에 도커파일 명시된것들이 다 바뀌지 않았었네요. 감사합니다
| on: | ||
| push: | ||
| branches: [ "release" ] | ||
| branches: [ "develop" ] |
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.
이제 develop에 머지되면 CD가 돌아가겠네요 🥳
환경변수도 바꿔두겠습니다! 폴더명도 생성해줘야해서 미루고 있었는데, 바꾸도록 하겠습니다 DNS 이름같은경우는 바꾸는데 좀 더 걸리기도 하고, 프론트엔드 uri도 일단은 stage로 되어있어서 유지할까 싶은데 어떠신가요? |
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.

관련 이슈
작업 내용
특이 사항
리뷰 요구사항 (선택)