Ec2 deploy 동작 순서 수정

[Hys-Lee]

ec2 인스턴스 용량 부족으로 인해 배포 순서 변경
기존 이미지 삭제 후 pull하는 방식으로 변경

Summary by CodeRabbit

• Chores
  • Streamlined the production deployment pipeline to use a standardized Docker build-and-push action.
  • Added a pre-deployment cleanup to ensure old containers are removed before deploying the new version.
  • Removed redundant stop/remove steps and minor formatting cleanup.
  • Impact: Improves deployment reliability and consistency, reducing potential downtime during releases. No changes to product functionality or user experience.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Updates the production deployment workflow to use docker/build-push-action@v4 for building/pushing the image, introduces an early pre-deploy container stop/remove on EC2, removes a duplicate stop/remove block later in the script, and applies a minor formatting tweak.

Changes

Cohort / File(s)	Summary of Changes
CI/CD workflow update \.github/workflows/production-deploy.yml	Replaced manual Docker build/push with docker/build-push-action@v4 (with context, push, tags, and build-args). Added pre-deploy cleanup on EC2 to stop/remove motimo-fe-production before pull/run. Removed redundant stop/remove block after pull. Minor formatting cleanup.

Sequence Diagram(s)

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

  Dev->>GH: Push to main / trigger workflow
  GH->>DH: Build & push image (docker/build-push-action@v4)\n(tags: ${DOCKERHUB_USERNAME}/motimo-fe-production:${{ github.sha }})
  Note right of GH: Pass build-args\nNEXT_PUBLIC_FRONTEND_BASE_URL

  GH->>EC2: SSH: Pre-deploy cleanup\n(stop & remove motimo-fe-production if running)
  GH->>EC2: Docker pull new image (by commit SHA tag)
  EC2->>EC2: Docker run motimo-fe-production\n(with existing run args)

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Ec2 deploy with Docker #59 — Also adjusts the same production deployment workflow for image build/push and container handling.
• Ec2 deploy 안정화 #60 — Modifies the deployment lifecycle in .github/workflows/production-deploy.yml focusing on stop/remove/run steps.
• Ec2 deploy 깃헙액션 docker관련 명령어 sudo추가 #61 — Edits the EC2 deploy script’s Docker commands within the same workflow file.

Poem

I hop through pipelines, light and keen,
New images baked, so fresh and clean.
Stop, remove—make room to run,
Pull the tag, deploy is done.
With whiskers twitching, logs all green—
Ship it swift, like a springtime scene. 🐇🚀

---

📜 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 c483b30 and aa970d6.

📒 Files selected for processing (1)

• .github/workflows/production-deploy.yml (1 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.