Skip to content

feat: point app at GCP api.soundlog.shop origin - #21

Open
manNomi wants to merge 1 commit into
mainfrom
feature/gcp-api-origin
Open

feat: point app at GCP api.soundlog.shop origin#21
manNomi wants to merge 1 commit into
mainfrom
feature/gcp-api-origin

Conversation

@manNomi

@manNomi manNomi commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Summary

  • SoundLogServer moved from AWS EC2 to a GCP Compute Engine VM, with Caddy terminating HTTPS for api.soundlog.shop directly on the VM (see SoundLogServer#19). Updates EXPO_PUBLIC_SOUNDLOG_API_BASE_URL in eas.json (development/preview/production) from https://soundlog.shop/api/soundlog to https://api.soundlog.shop so the app calls the API directly instead of through the Vercel rewrite proxy.
  • Updates docs/deployment/SOUNDLOG_SHOP_DOMAIN.md and README.md to describe the new api.soundlog.shop A record and the updated env values.
  • Important: scripts/require-vercel-api-origin.js had https://api.soundlog.shop deny-listed in staleOrigins from an earlier iteration of the project (before it moved to the EC2 + Vercel-proxy setup this PR is replacing). Removed it from that list — otherwise the Vercel web build would immediately fail once SOUNDLOG_API_ORIGIN is set back to this value. Also fixed stale EC2 references in scripts/check-api-origin.js and scripts/check-server-web-export.js error/usage messages.

Manual step required (blocking)

api.soundlog.shop needs a Gabia DNS A record → 34.64.116.40 (the new GCP static IP) before https://api.soundlog.shop resolves. See SoundLogServer#19 for details.

Related

  • SoundLogServer PR (GCP deploy, already verified working internally): feat: replace EC2 deploy with GCP Compute Engine SoundLogServer#19
  • The sound-log-app Vercel project's SOUNDLOG_API_ORIGIN env var (Production + Preview) has already been updated to https://api.soundlog.shop. The next web deploy needs this PR merged first, since the stale-origin guard fix lives here.

Test plan

  • node -c on the three edited scripts, eas.json JSON-validated
  • npm run check:api-origin -- https://api.soundlog.shop once DNS is live
  • EAS development/preview build smoke test against the new origin
  • Trigger a Vercel redeploy of sound-log-app after merge and confirm the build passes the origin guard

🤖 Generated with Claude Code

SoundLogServer moved from AWS EC2 to a GCP Compute Engine VM, with
Caddy terminating HTTPS for api.soundlog.shop directly on the VM.
Updates EAS build env, docs, and the Vercel API-origin guard scripts
to match (api.soundlog.shop was previously deny-listed as a stale
origin from an earlier iteration; it's the current origin again).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sound-log-app Ready Ready Preview, Comment Jul 28, 2026 5:45am

@manNomi

manNomi commented Jul 28, 2026

Copy link
Copy Markdown
Contributor Author

남은 할 일 (TODO)

  • Gabia DNS: api.soundlog.shop A 레코드 → 34.64.116.40 추가 (자세한 내용은 SoundLogServer#19)
  • 이 PR과 SoundLogServer#19 리뷰 후 머지
  • 머지 후 Vercel sound-log-app 프로젝트 재배포 트리거 (main에 남아있던 stale-origin 가드가 이 PR로 수정되므로, 머지 전에 재배포하면 빌드 실패함)
  • DNS 반영 후 npm run check:api-origin -- https://api.soundlog.shop 실행해서 최종 검증
  • EAS development/preview 빌드로 실기기 스모크 테스트

검증 완료

  • npm run check:vercel-config 통과 — vercel.mjs에 origin 하드코딩 없음, rewrite 구조 정상
  • SOUNDLOG_API_ORIGIN=https://api.soundlog.shop node scripts/require-vercel-api-origin.js — 더 이상 stale로 거부되지 않음 확인
  • 옛 EC2 IP(http://52.79.185.121:4000)는 여전히 stale로 정상 거부되는 것 확인 (가드 로직 자체는 유지됨)
  • npm run typecheck 통과
  • Vercel sound-log-app 프로젝트의 SOUNDLOG_API_ORIGIN env(Production/Preview)를 https://api.soundlog.shop으로 이미 갱신함

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.

1 participant