docs(server): DuckDNS+Let's Encrypt HTTPS 적용 반영 (#47) - #86
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughCLAUDE.md의 배포 문서에서 API 베이스 URL이 HTTP 기반 EC2 호스트 주소에서 DuckDNS 도메인과 Let’s Encrypt를 사용하는 HTTPS 주소로 변경되었습니다. 인증서 경로, 갱신 스케줄, 커스텀 도메인 적용 조건과 SSM 파라미터 항목도 함께 구체화되었습니다. Changes배포 문서 업데이트
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
무엇을 / 왜
백엔드 API에 HTTPS 적용 완료(DuckDNS 무료 도메인 + Let's Encrypt). 프론트(Vercel, HTTPS)에서 HTTP API를 호출하면 브라우저가 Mixed Content로 차단하는 문제를 막기 위해 필요했음. AWS 크레딧이 Route 53 도메인 등록에는 적용되지 않아 무료인 DuckDNS로 결정.
변경 사항
https://thumbsup-api.duckdns.org/로 갱신관련 이슈
Refs #47 (배포 파이프라인 실전 검증이 아직 남아있어 아직 Closes 아님)
체크리스트
https://thumbsup-api.duckdns.org/외부 접속 확인(502, 앱 미배포로 정상), HTTP→HTTPS 리다이렉트(301) 확인, 인증서 갱신 dry-run 성공Summary by CodeRabbit