Ec2 deploy 자동 배포 완성

[Hys-Lee]

cd과정의 에러 모두 수정했습니다.

추가로 로그인 화면 제스처 바도 삭제했습니다.

Summary by CodeRabbit

• Chores
  • Streamlined production deployment pipeline to use a standardized Docker build-and-push action for more consistent releases.
  • Added build-time environment configuration to better align production builds with runtime settings.
  • Introduced automatic cleanup on the server before deployment to prevent disk space issues and improve reliability.
  • No changes to app functionality or user experience; deployments should be more stable and predictable.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Workflow updates in .github/workflows/production-deploy.yml replace manual Docker build/push with docker/build-push-action@v4 (including a build arg), adjust image tagging to use the commit SHA, and add a docker system prune on the EC2 host before pulling and restarting the container. The deploy sequence otherwise remains unchanged.

Changes

Cohort / File(s)	Summary
CI/CD workflow update .github/workflows/production-deploy.yml	- Replace manual docker build/push with docker/build-push-action@v4 (context .; push true; tag ${DOCKERHUB_USERNAME}/motimo-fe-production:${{ github.sha }}; build-arg NEXT_PUBLIC_FRONTEND_BASE_URL from secrets) - Add EC2 pre-pull cleanup: sudo docker system prune -a -f - Keep pull/stop/rm/run steps; minor comments added; trigger unchanged

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor Dev as Developer
  participant GH as GitHub Actions
  participant DH as Docker Hub
  participant EC2 as EC2 Host
  participant Docker as Docker Engine

  Dev->>GH: Push to production branch
  GH->>GH: Build image (docker/build-push-action@v4)<br/>with build-arg from secrets
  GH->>DH: Push image tagged with commit SHA
  GH->>EC2: SSH and run deploy script
  EC2->>Docker: system prune -a -f (cleanup)
  EC2->>DH: Pull image by SHA tag
  EC2->>Docker: Stop & remove existing container
  EC2->>Docker: Run new container (ports, env-file)
  note over EC2,Docker: Flow unchanged after prune

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Ec2 deploy 깃헙액션 docker관련 명령어 sudo추가 #61 — Also modifies the same workflow’s Docker commands; complements this PR’s switch to build-push action and adds sudo usage.
• Ec2 deploy with Docker #59 — Introduces the initial production-deploy workflow that this PR updates with build-push v4 and EC2 prune.

Poem

A bunny pressed “Deploy!” with glee,
New images hop to registry.
A tidy warren: prune and sweep,
Then pull a tag from commit-deep.
Ports aligned, the carrots glow—
Ship it quick, and off we go! 🥕🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 797a80c and 57eb613.

📒 Files selected for processing (1)

• .github/workflows/production-deploy.yml (3 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

🪧 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.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbit in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbit 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:
  • @coderabbit gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbit read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbit help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbit ignore or @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbit summary or @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbit or @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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.