ui 버그, 배포스크립트 버그 수정

[rktclgh]

📢 기능 설명

필요시 실행결과 스크린샷 첨부

연결된 issue

연결된 issue를 자동으로 닫기 위해 아래 {이슈넘버}를 입력해주세요.

close #{이슈넘버}

🩷 Approve 하기 전 확인해주세요!

• 리뷰어가 확인해줬으면 하는 사항 적어주세요.
• [ ]

✅ 체크리스트

• PR 제목 규칙 잘 지켰는가?
• 추가/수정사항을 설명하였는가?
• 이슈넘버를 적었는가?
• Approve 하기 전 확인 사항 체크했는가?

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2f8a8fd8-d3b1-4261-b509-866bb1eed182

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch develop

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

이 PR은 블루-그린 배포 프로세스를 강화하여 UI 및 배포 스크립트 버그를 해결합니다. 더 견고한 헬스 및 프록시 체크를 도입하여 배포의 신뢰성을 높이고, 프록시가 새 애플리케이션 인스턴스로 올바르게 전환되지 않을 수 있는 잠재적인 문제를 방지합니다.

Highlights

• 배포 스크립트 개선: 프록시 헬스체크 및 curl 타임아웃을 위한 새로운 환경 변수들이 추가되었습니다.
• 향상된 헬스체크: 헬스체크 중 더 나은 제어를 위해 curl 명령어에 max-time 옵션이 추가되었습니다.
• 강화된 프록시 검증: 프록시 스위칭 후 Nginx 설정이 새 업스트림을 올바르게 반영하는지 확인하는 로직이 도입되었습니다.
• 설정 가능한 프록시 체크 경로: 프록시 헬스체크가 이제 애플리케이션의 헬스 경로 대신 설정 가능한 경로(PROXY_CHECK_PATH)를 사용합니다.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request significantly enhances the blue-green deployment script by introducing more robust health and proxy checking mechanisms. It adds new configurable environment variables for proxy check path, timeouts, and curl max time. The curl commands for both application health checks and proxy response checks now include a --max-time option. A critical improvement is the addition of a verification step after proxy switching, which checks if the Nginx configuration has been correctly updated to point to the new upstream server. The proxy response check now uses a dedicated path and configurable timeout. I have no feedback to provide.