. 🚀 Phase 10 — CI/CD with Zero Downtime (Production Setup)

[vimal-java-dev]

We’ll build this in 4 controlled layers (don’t skip order):

🧩 Architecture Overview (What we are building)

GitHub Push
↓
GitHub Actions
↓
Build Docker Image
↓
Push to GHCR
↓
SSH into VPS
↓
Pull New Image
↓
Zero-downtime Deployment (Blue-Green)

---

✅ STEP 1 — Prepare VPS for Automated Deploy

You already have:

• ✅ Docker running
• ✅ App deployed
• ✅ Domain working
• ✅ Prometheus + Grafana

Now we make VPS CI/CD-ready

[vimal-tech-dev]

Assign me.

[vimal-tech-dev]

We’ll build this in 4 controlled layers (don’t skip order):

🧩 Architecture Overview (What we are building)

GitHub Push ↓ GitHub Actions ↓ Build Docker Image ↓ Push to GHCR ↓ SSH into VPS ↓ Pull New Image ↓ Zero-downtime Deployment (Blue-Green)

✅ STEP 1 — Prepare VPS for Automated Deploy

You already have:

• ✅ Docker running
• ✅ App deployed
• ✅ Domain working
• ✅ Prometheus + Grafana

Now we make VPS CI/CD-ready

Made a new Docker Compose file under this package for CI/CD to run independently

/deployments/contact-api

By replacing with things below,

networks:
app-network:
external: true
name: vimaltech-contact-api_app-network

monitoring-network:
external: true
name: vimaltech-contact-api_monitoring-network

---

Copy .env for new compose file.

cp ~/vimaltech-contact-api/.env ~/deployments/contact-api/

All of the above is for the Spring Boot environment setup for Step 1.

---

✅ STEP 1 — COMPLETE

You now have:

✔ App running via Docker Compose
✔ Connected to existing Postgres + Redis
✔ Correct network bridging
✔ Environment variables properly wired
✔ Health check returning UP

[vimal-java-dev]

🚀 Now Moving Forward

🔐 STEP 2 — Secure GitHub → VPS Access (SSH Automation)

This is where your deployment becomes:

👉 Fully automatic on every push

[vimal-tech-dev]

I’ve added all 3 secrets to the main repo(Owner) settings.

• VPS_HOST
• VPS_USER
• VPS_SSH_KEY

[vimal-java-dev]

Perfect—this is where your system becomes fully automated. Let’s wire it cleanly.

🚀 STEP 3 — CI/CD Pipeline (Build → Push → Deploy)

We’ll now make:

👉 git push → auto deploy to VPS

🧩 What This Pipeline Will Do

1. Build Docker image
2. Push to GHCR (GitHub Container Registry)
3. SSH into VPS
4. Pull the latest image
5. Restart the container

[vimal-java-dev]

PR #35 is merged and closed.

[vimal-java-dev]

Current state:

• CI/CD pipeline working (GitHub Actions → GHCR → VPS deploy)
• App running via Docker Compose
• Postgres + Redis running separately
• NGINX installed (nginx/1.24.0)
• App exposed via 127.0.0.1:8080

Goal:

• Implement Blue-Green deployment
• Zero downtime releases
• Health-check-based switching
• Rollback safety

Proceed step-by-step like a senior DevOps engineer.

[vimal-tech-dev]

Current state:

• CI/CD pipeline working (GitHub Actions → GHCR → VPS deploy)
• App running via Docker Compose
• Postgres + Redis running separately
• NGINX installed (nginx/1.24.0)
• App exposed via 127.0.0.1:8080

Goal:

• Implement Blue-Green deployment
• Zero downtime releases
• Health-check-based switching
• Rollback safety

Proceed step-by-step like a senior DevOps engineer.

What I Just Achieved
I now have:

✅ True Blue-Green deployment
✅ Zero downtime switching
✅ Verified production routing
✅ Repeatable deployment model
✅ Instant rollback capability

[vimal-java-dev]

🧠 Senior-Level Insight

At this point, your system behaviour matches:

AWS / Kubernetes / Netflix-style deployment pattern

You’re no longer doing “deploy & restart” —
You’re doing traffic-controlled releases.

[vimal-tech-dev]

Continuing backend DevOps project (Spring Boot)

Completed:

• CI/CD pipeline (GitHub Actions → GHCR → VPS)
• Dockerized app
• Postgres + Redis (separate infra)
• NGINX with SSL (api.vimaltech.dev)
• Prometheus + Grafana monitoring
• Blue-Green deployment (zero downtime)
  • app_blue (8081)
  • app_green (8082)
  • NGINX upstream switching is working
  • Health checks implemented
  • Manual switching + rollback working
  • GREEN currently lives
  • /home/deploy/current_env used for tracking