Skip to content

πŸ’‘ ν”„λ‘œλ•μ…˜ 배포 μ›Œν¬ν”Œλ‘œμš°κ°€ HTTPS ν™˜κ²½μ— 맞게 이름과 트리거 λΈŒλžœμΉ˜κ°€ λ³€κ²½ - #123

Merged
passionryu merged 1 commit into
devfrom
feat/https
Jul 22, 2025

Conversation

@moonjun1

@moonjun1 moonjun1 commented Jul 22, 2025

Copy link
Copy Markdown
Member

πŸ’‘ λ¦¬λ‹€μ΄λ ‰νŠΈ: https://likelionnews.click/?error=true 주석 μΆ”κ°€ localhost μΆ”κ°€

Summary by CodeRabbit

  • Chores
    • ν”„λ‘œλ•μ…˜ 배포 μ›Œν¬ν”Œλ‘œμš°κ°€ HTTPS ν™˜κ²½μ— 맞게 이름과 트리거 λΈŒλžœμΉ˜κ°€ λ³€κ²½λ˜μ—ˆμŠ΅λ‹ˆλ‹€.
    • 배포 ν›„ μ»¨ν…Œμ΄λ„ˆ μƒνƒœ 확인 및 λ‚΄λΆ€/μ™ΈλΆ€ ν—¬μŠ€μ²΄ν¬κ°€ κ°„μ†Œν™”λ˜κ³  HTTPS μ—”λ“œν¬μΈνŠΈλ‘œ 검증이 κ°•ν™”λ˜μ—ˆμŠ΅λ‹ˆλ‹€.
    • 배포 μš”μ•½ μ•ˆλ‚΄μ— HTTPS μ£Όμ†Œ 및 μΆ”κ°€ 점검 방법이 ν¬ν•¨λ˜μ—ˆμŠ΅λ‹ˆλ‹€.

@coderabbitai

coderabbitai Bot commented Jul 22, 2025

Copy link
Copy Markdown

Walkthrough

ν”„λ‘œλ•μ…˜ 배포용 GitHub Actions μ›Œν¬ν”Œλ‘œμš°κ°€ HTTPS 지원에 맞게 이름과 트리거 브랜치λ₯Ό λ³€κ²½ν•˜κ³ , 디버깅 및 μ»¨ν…Œμ΄λ„ˆ μƒνƒœ 확인, ν—¬μŠ€μ²΄ν¬ 단계가 κ°„μ†Œν™” 및 HTTPS 기반으둜 κ°œνŽΈλ˜μ—ˆμŠ΅λ‹ˆλ‹€. μ»¨ν…Œμ΄λ„ˆλ³„ κ°œλ³„ ν…ŒμŠ€νŠΈκ°€ 제거되고, λ‚΄λΆ€ 및 μ™ΈλΆ€ ν—¬μŠ€μ²΄ν¬κ°€ κ°•ν™”λ˜μ—ˆμŠ΅λ‹ˆλ‹€.

Changes

파일/경둜 λ³€κ²½ μš”μ•½
.github/workflows/deploy-prod.yml μ›Œν¬ν”Œλ‘œμš° 이름 및 트리거 브랜치 λ³€κ²½, 디버깅/μƒνƒœν™•μΈ/ν—¬μŠ€μ²΄ν¬ 단계 개편, HTTPS μ—”λ“œν¬μΈνŠΈ 검증 κ°•ν™”

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHubActions
    participant EC2
    participant Docker
    participant SpringBoot
    participant MySQL
    participant Redis
    participant Elasticsearch
    participant ALB

    Developer->>GitHubActions: Push to feat/https 브랜치
    GitHubActions->>EC2: 배포 슀크립트 μ‹€ν–‰
    EC2->>Docker: μ»¨ν…Œμ΄λ„ˆ μƒνƒœ 확인 (ps, logs)
    EC2->>Docker: MySQL/Redis/Elasticsearch μ»¨ν…Œμ΄λ„ˆ 쑴재 μ—¬λΆ€ 확인
    EC2->>SpringBoot: λ‚΄λΆ€ ν—¬μŠ€μ²΄ν¬ (curl localhost:8080)
    EC2->>ALB: HTTPS μ—”λ“œν¬μΈνŠΈ ν—¬μŠ€μ²΄ν¬ (curl https://api.likelionnews.click)
    GitHubActions->>Developer: 배포 μš”μ•½ 및 μƒνƒœ 리포트
Loading

Estimated code review effort

2 (~15λΆ„)

Possibly related PRs

  • News-Deliver/Server#98: Nginx reverse proxy 제거 및 μ»¨ν…Œμ΄λ„ˆ ν…ŒμŠ€νŠΈ/디버깅 단계 μˆ˜μ • λ“±, 동일 μ›Œν¬ν”Œλ‘œμš° 파일과 μ»¨ν…Œμ΄λ„ˆ ν—¬μŠ€μ²΄ν¬ κ΄€λ ¨ 뢀뢄을 μˆ˜μ •ν•˜μ—¬ 배포 및 μ»¨ν…Œμ΄λ„ˆ μƒνƒœ 검증에 μ΄ˆμ μ„ 맞좘 κ΄€λ ¨ PRμž…λ‹ˆλ‹€.

πŸͺ§ Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (3)
.github/workflows/deploy-prod.yml (3)

58-96: 곡백·trailing spaces 제거둜 YAMLLint 였λ₯˜ ν•΄κ²° ν•„μš”

YAML Lintμ—μ„œ μ§€μ λœ trailing spaceκ°€ 이 ꡬ간에 λ‹€μˆ˜ μ‘΄μž¬ν•©λ‹ˆλ‹€. CI νŒŒμ΄ν”„λΌμΈμ— 영ν–₯은 μ—†μ§€λ§Œ, PR μžμ²΄κ°€ β€œHTTPS λŒ€μ‘β€μ˜ 신뒰성을 κ°•μ‘°ν•˜λŠ” 만큼 린트 였λ₯˜λŠ” 정리해 λ‘λŠ” 편이 μ’‹μŠ΅λ‹ˆλ‹€.

-            echo "=== Docker μ»¨ν…Œμ΄λ„ˆ μƒνƒœ ==="␠
+            echo "=== Docker μ»¨ν…Œμ΄λ„ˆ μƒνƒœ ==="
...
-            # Redis 확인␠ 
+            # Redis 확인

Also applies to: 63-66, 74-95


75-95: μ»¨ν…Œμ΄λ„ˆ 쑴재 μ—¬λΆ€ 체크 μ‹œ substring μ˜€κ²€μΆœ μœ„ν—˜

docker ps | grep -q mysql ν˜•νƒœλŠ” mysql-client, dummy-mysql λ“± μ˜ˆμƒμΉ˜ λͺ»ν•œ μ΄λ¦„κΉŒμ§€ κΈμ–΄μ˜¬ 수 μžˆμŠ΅λ‹ˆλ‹€. ν•„ν„°λ₯Ό λͺ…μ‹œμ μœΌλ‘œ μ‚¬μš©ν•΄ μ˜€νƒμ„ 쀄여 μ£Όμ„Έμš”.

-if docker ps | grep -q mysql; then
+if docker ps --filter "name=mysql" --format '{{.Names}}' | grep -q .; then

동일 νŒ¨ν„΄μ„ RedisΒ·Elasticsearch에도 μ μš©ν•˜λ©΄ μ’‹μŠ΅λ‹ˆλ‹€.


115-169: μ΅œμ’… HTTPS ν—¬μŠ€μ²΄ν¬μ—μ„œ 30x 응닡 처리 및 success ν”Œλž˜κ·Έ 둜직 확보

  1. μ‹€μ œ 운영 ν™˜κ²½μ—μ„œ ALB β†’ Target Group κ°„ λ¦¬λ‹€μ΄λ ‰νŠΈ(301/302)κ°€ μžˆμ„ 수 μžˆμŠ΅λ‹ˆλ‹€. ν˜„μž¬ λ‘œμ§μ€ 200만 μ„±κ³΅μœΌλ‘œ νŒλ‹¨ν•˜μ—¬ λΆˆν•„μš”ν•œ μ‹€νŒ¨λ₯Ό μœ λ°œν•  수 μžˆμŠ΅λ‹ˆλ‹€.
  2. success=true μ„€μ • ν›„ break 2 λ‘œν”„λ₯Ό λΉ μ Έλ‚˜μ˜€μ§€λ§Œ, μ„œλΈŒμ…Έμ΄ μ•„λ‹Œμ§€ ν™•μΈν•˜λ €λ©΄ set -o pipefail μ‚¬μš©μ„ ꢌμž₯ν•©λ‹ˆλ‹€.
-if [ "$http_code" = "200" ]; then
+if [[ "$http_code" =~ ^(200|301|302)$ ]]; then
   echo "  βœ… $endpoint 성곡!"
   success=true
   break 2
πŸ“œ Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between e2352ef and 4d18d71.

πŸ“’ Files selected for processing (1)
  • .github/workflows/deploy-prod.yml (4 hunks)
πŸͺ› YAMLlint (1.37.1)
.github/workflows/deploy-prod.yml

[error] 63-63: trailing spaces

(trailing-spaces)


[error] 66-66: trailing spaces

(trailing-spaces)


[error] 74-74: trailing spaces

(trailing-spaces)


[error] 82-82: trailing spaces

(trailing-spaces)


[error] 83-83: trailing spaces

(trailing-spaces)


[error] 89-89: trailing spaces

(trailing-spaces)


[error] 102-102: trailing spaces

(trailing-spaces)


[error] 109-109: trailing spaces

(trailing-spaces)


[error] 118-118: trailing spaces

(trailing-spaces)


[error] 121-121: trailing spaces

(trailing-spaces)


[error] 124-124: trailing spaces

(trailing-spaces)


[error] 127-127: trailing spaces

(trailing-spaces)


[error] 131-131: trailing spaces

(trailing-spaces)


[error] 188-188: no new line character at the end of file

(new-line-at-end-of-file)

🧰 Additional context used
πŸͺ› YAMLlint (1.37.1)
.github/workflows/deploy-prod.yml

[error] 63-63: trailing spaces

(trailing-spaces)


[error] 66-66: trailing spaces

(trailing-spaces)


[error] 74-74: trailing spaces

(trailing-spaces)


[error] 82-82: trailing spaces

(trailing-spaces)


[error] 83-83: trailing spaces

(trailing-spaces)


[error] 89-89: trailing spaces

(trailing-spaces)


[error] 102-102: trailing spaces

(trailing-spaces)


[error] 109-109: trailing spaces

(trailing-spaces)


[error] 118-118: trailing spaces

(trailing-spaces)


[error] 121-121: trailing spaces

(trailing-spaces)


[error] 124-124: trailing spaces

(trailing-spaces)


[error] 127-127: trailing spaces

(trailing-spaces)


[error] 131-131: trailing spaces

(trailing-spaces)


[error] 188-188: no new line character at the end of file

(new-line-at-end-of-file)

πŸ”‡ Additional comments (1)
.github/workflows/deploy-prod.yml (1)

1-8: μ›Œν¬ν”Œλ‘œ 트리거 브랜치 μž¬κ²€ν† 

master + feat/https 두 브랜치 λͺ¨λ‘ ν‘Έμ‹œ νŠΈλ¦¬κ±°μ— ν¬ν•¨λ˜μ—ˆμŠ΅λ‹ˆλ‹€.

  • main 을 μ‚¬μš©ν•˜λŠ” 레포라면 μ˜€μž‘λ™ν•  수 있고,
  • PR μ „μš© 브랜치(feat/https)λŠ” λ¨Έμ§€ ν›„ μ‚­μ œλ  κ°€λŠ₯성도 μžˆμŠ΅λ‹ˆλ‹€.

λΆˆν•„μš”ν•œ 쀑볡 νŠΈλ¦¬κ±°κ°€ μžˆλŠ”μ§€ 확인해 μ£Όμ„Έμš”.

Comment on lines +98 to 113
- name: λ‚΄λΆ€ ν—¬μŠ€μ²΄ν¬
run: |
ssh -i ~/.ssh/id_rsa ${{ secrets.EC2_USERNAME }}@${{ secrets.EC2_HOST }} '
echo "πŸ₯ λ‚΄λΆ€ ν—¬μŠ€μ²΄ν¬ μ‹œμž‘"

echo "=== Spring Boot μ»¨ν…Œμ΄λ„ˆ 직접 ν…ŒμŠ€νŠΈ ==="
# Spring Boot μ»¨ν…Œμ΄λ„ˆ λ‚΄λΆ€μ—μ„œ μžκ°€ ν…ŒμŠ€νŠΈ
SPRINGBOOT_CONTAINER=$(docker ps -q --filter "name=springboot")
if [ ! -z "$SPRINGBOOT_CONTAINER" ]; then
echo "Spring Boot μ»¨ν…Œμ΄λ„ˆ λ‚΄λΆ€ ν”„λ‘œμ„ΈμŠ€:"
docker exec $SPRINGBOOT_CONTAINER ps aux || echo "ν”„λ‘œμ„ΈμŠ€ 확인 μ‹€νŒ¨"

echo "Spring Boot μ»¨ν…Œμ΄λ„ˆ λ„€νŠΈμ›Œν¬ 확인:"
docker exec $SPRINGBOOT_CONTAINER netstat -tulpn 2>/dev/null || docker exec $SPRINGBOOT_CONTAINER ss -tulpn || echo "λ„€νŠΈμ›Œν¬ μƒνƒœ 확인 μ‹€νŒ¨"

echo "Spring Boot λ‚΄λΆ€μ—μ„œ μžκ°€ ν…ŒμŠ€νŠΈ:"
docker exec $SPRINGBOOT_CONTAINER curl -f http://localhost:8080/api/auth/status || echo "λ‚΄λΆ€ μžκ°€ ν…ŒμŠ€νŠΈ μ‹€νŒ¨"
else
echo "Spring Boot μ»¨ν…Œμ΄λ„ˆκ°€ μ‹€ν–‰ 쀑이 μ•„λ‹™λ‹ˆλ‹€"
echo "Spring Boot λ‚΄λΆ€ ν—¬μŠ€μ²΄ν¬:"
docker exec $SPRINGBOOT_CONTAINER curl -f http://localhost:8080/api/auth/status 2>/dev/null && echo "βœ… λ‚΄λΆ€ API 정상" || echo "❌ λ‚΄λΆ€ API μ‹€νŒ¨"
fi

echo "πŸ§ͺ μ»¨ν…Œμ΄λ„ˆλ³„ κ°œλ³„ ν…ŒμŠ€νŠΈ μ™„λ£Œ"
# ν˜ΈμŠ€νŠΈμ—μ„œ μ»¨ν…Œμ΄λ„ˆλ‘œ μ ‘κ·Ό ν…ŒμŠ€νŠΈ
echo "ν˜ΈμŠ€νŠΈμ—μ„œ μ»¨ν…Œμ΄λ„ˆ μ ‘κ·Ό ν…ŒμŠ€νŠΈ:"
curl -f http://localhost:8080/api/auth/status 2>/dev/null && echo "βœ… 호슀트->μ»¨ν…Œμ΄λ„ˆ 정상" || echo "❌ 호슀트->μ»¨ν…Œμ΄λ„ˆ μ‹€νŒ¨"
'

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

πŸ› οΈ Refactor suggestion

λ‚΄λΆ€ ν—¬μŠ€μ²΄ν¬ μŠ€ν¬λ¦½νŠΈμ— μ¦‰μ‹œ μ‹€νŒ¨(set -e) 및 λͺ…ν™•ν•œ λ°˜ν™˜κ°’ 반영 ꢌμž₯

ν˜„μž¬ μŠ€ν¬λ¦½νŠΈλŠ” curl μ‹€νŒ¨ μ‹œμ—λ„ SSH μ„Έμ…˜ μžμ²΄λŠ” 계속 μ§„ν–‰λ©λ‹ˆλ‹€. 배포 성곡 μ—¬λΆ€λ₯Ό μ •ν™•νžˆ λ°˜μ˜ν•˜λ €λ©΄ λ‚΄λΆ€ ν—¬μŠ€μ²΄ν¬ λ‹¨κ³„μ—μ„œλ„ set -euo pipefail을 μ„ μ–Έν•˜κ³ , μ‹€νŒ¨ μ‹œ exit 1둜 μ›Œν¬ν”Œλ‘œ 전체λ₯Ό μ€‘λ‹¨ν•˜λ„λ‘ μ„€μ •ν•˜λŠ” 편이 μ•ˆμ „ν•©λ‹ˆλ‹€.

-run: |
+run: |
+  set -euo pipefail
   ssh -i ~/.ssh/id_rsa ${{ secrets.EC2_USERNAME }}@${{ secrets.EC2_HOST }} '
     set -euo pipefail
     ...
     docker exec $SPRINGBOOT_CONTAINER curl -fsS http://localhost:8080/api/auth/status \
       && echo "βœ… λ‚΄λΆ€ API 정상" \
       || { echo "❌ λ‚΄λΆ€ API μ‹€νŒ¨"; exit 1; }
πŸ“ Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: λ‚΄λΆ€ ν—¬μŠ€μ²΄ν¬
run: |
ssh -i ~/.ssh/id_rsa ${{ secrets.EC2_USERNAME }}@${{ secrets.EC2_HOST }} '
echo "πŸ₯ λ‚΄λΆ€ ν—¬μŠ€μ²΄ν¬ μ‹œμž‘"
echo "=== Spring Boot μ»¨ν…Œμ΄λ„ˆ 직접 ν…ŒμŠ€νŠΈ ==="
# Spring Boot μ»¨ν…Œμ΄λ„ˆ λ‚΄λΆ€μ—μ„œ μžκ°€ ν…ŒμŠ€νŠΈ
SPRINGBOOT_CONTAINER=$(docker ps -q --filter "name=springboot")
if [ ! -z "$SPRINGBOOT_CONTAINER" ]; then
echo "Spring Boot μ»¨ν…Œμ΄λ„ˆ λ‚΄λΆ€ ν”„λ‘œμ„ΈμŠ€:"
docker exec $SPRINGBOOT_CONTAINER ps aux || echo "ν”„λ‘œμ„ΈμŠ€ 확인 μ‹€νŒ¨"
echo "Spring Boot μ»¨ν…Œμ΄λ„ˆ λ„€νŠΈμ›Œν¬ 확인:"
docker exec $SPRINGBOOT_CONTAINER netstat -tulpn 2>/dev/null || docker exec $SPRINGBOOT_CONTAINER ss -tulpn || echo "λ„€νŠΈμ›Œν¬ μƒνƒœ 확인 μ‹€νŒ¨"
echo "Spring Boot λ‚΄λΆ€μ—μ„œ μžκ°€ ν…ŒμŠ€νŠΈ:"
docker exec $SPRINGBOOT_CONTAINER curl -f http://localhost:8080/api/auth/status || echo "λ‚΄λΆ€ μžκ°€ ν…ŒμŠ€νŠΈ μ‹€νŒ¨"
else
echo "Spring Boot μ»¨ν…Œμ΄λ„ˆκ°€ μ‹€ν–‰ 쀑이 μ•„λ‹™λ‹ˆλ‹€"
echo "Spring Boot λ‚΄λΆ€ ν—¬μŠ€μ²΄ν¬:"
docker exec $SPRINGBOOT_CONTAINER curl -f http://localhost:8080/api/auth/status 2>/dev/null && echo "βœ… λ‚΄λΆ€ API 정상" || echo "❌ λ‚΄λΆ€ API μ‹€νŒ¨"
fi
echo "πŸ§ͺ μ»¨ν…Œμ΄λ„ˆλ³„ κ°œλ³„ ν…ŒμŠ€νŠΈ μ™„λ£Œ"
# ν˜ΈμŠ€νŠΈμ—μ„œ μ»¨ν…Œμ΄λ„ˆλ‘œ μ ‘κ·Ό ν…ŒμŠ€νŠΈ
echo "ν˜ΈμŠ€νŠΈμ—μ„œ μ»¨ν…Œμ΄λ„ˆ μ ‘κ·Ό ν…ŒμŠ€νŠΈ:"
curl -f http://localhost:8080/api/auth/status 2>/dev/null && echo "βœ… 호슀트->μ»¨ν…Œμ΄λ„ˆ 정상" || echo "❌ 호슀트->μ»¨ν…Œμ΄λ„ˆ μ‹€νŒ¨"
'
- name: λ‚΄λΆ€ ν—¬μŠ€μ²΄ν¬
run: |
set -euo pipefail
ssh -i ~/.ssh/id_rsa ${{ secrets.EC2_USERNAME }}@${{ secrets.EC2_HOST }} '
set -euo pipefail
echo "πŸ₯ λ‚΄λΆ€ ν—¬μŠ€μ²΄ν¬ μ‹œμž‘"
# Spring Boot μ»¨ν…Œμ΄λ„ˆ λ‚΄λΆ€μ—μ„œ μžκ°€ ν…ŒμŠ€νŠΈ
SPRINGBOOT_CONTAINER=$(docker ps -q --filter "name=springboot")
if [ ! -z "$SPRINGBOOT_CONTAINER" ]; then
echo "Spring Boot λ‚΄λΆ€ ν—¬μŠ€μ²΄ν¬:"
docker exec $SPRINGBOOT_CONTAINER curl -fsS http://localhost:8080/api/auth/status \
&& echo "βœ… λ‚΄λΆ€ API 정상" \
|| { echo "❌ λ‚΄λΆ€ API μ‹€νŒ¨"; exit 1; }
fi
# ν˜ΈμŠ€νŠΈμ—μ„œ μ»¨ν…Œμ΄λ„ˆλ‘œ μ ‘κ·Ό ν…ŒμŠ€νŠΈ
echo "ν˜ΈμŠ€νŠΈμ—μ„œ μ»¨ν…Œμ΄λ„ˆ μ ‘κ·Ό ν…ŒμŠ€νŠΈ:"
curl -f http://localhost:8080/api/auth/status 2>/dev/null && echo "βœ… 호슀트->μ»¨ν…Œμ΄λ„ˆ 정상" || echo "❌ 호슀트->μ»¨ν…Œμ΄λ„ˆ μ‹€νŒ¨"
'
🧰 Tools
πŸͺ› YAMLlint (1.37.1)

[error] 102-102: trailing spaces

(trailing-spaces)


[error] 109-109: trailing spaces

(trailing-spaces)

πŸ€– Prompt for AI Agents
In .github/workflows/deploy-prod.yml around lines 98 to 113, the internal health
check script does not immediately fail on errors, which can cause the deployment
to proceed despite failures. To fix this, add 'set -euo pipefail' at the start
of the SSH command block to enable immediate exit on any error or unset
variable, and ensure that if any curl command fails, the script exits with 'exit
1' to properly signal failure and stop the workflow.

@moonjun1 moonjun1 changed the title πŸ’‘ λ¦¬λ‹€μ΄λ ‰νŠΈ: https://likelionnews.click/?error=true 주석 μΆ”κ°€ localhost μΆ”κ°€ πŸ’‘ ν”„λ‘œλ•μ…˜ 배포 μ›Œν¬ν”Œλ‘œμš°κ°€ HTTPS ν™˜κ²½μ— 맞게 이름과 트리거 λΈŒλžœμΉ˜κ°€ λ³€κ²½ Jul 22, 2025
@passionryu
passionryu merged commit 3719f0d into dev Jul 22, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants