How amitabh-devops/dev-gemini-clone works
Project type and purpose
• This is a full-stack web application (“Google Gemini Clone”) built with Next.js (React + Node).
• It’s production-grade with a full DevSecOps pipeline: CI/CD using Jenkins, GitOps via ArgoCD, Infrastructure as Code via Terraform, containerization with Docker/Kubernetes on AWS EKS, and observability with Prometheus/Grafana.
File structure
• Top‐level infra code:
• terraform/ (EC2 + Jenkins provisioning)
• Terraform-EKS-Deployment/ (EKS cluster provisioning)
• kubernetes/ (K8s manifests: Namespace, Deployments, Services, Ingress, ConfigMap, Secrets, HPA)
• GitOps/Jenkinsfile & Jenkinsfile in root for CI/CD pipelines.
• Application code under src/:
• A Next.js “app router” structure (routes, layout.tsx, page.tsx).
• API routes (src/app/api/auth/… using NextAuth).
• Models (chat.model.ts, user.model.ts), utilities (db.ts, theme providers), and atomic/react components.
• Config files: Dockerfile, docker-compose.yml, next.config.mjs, tsconfig.json, Tailwind CSS config.
• CI/CD & DevOps docs: DOCKER_BUILD.md, ENV_SETUP.md, DOCKERIGNORE, .env.sample.
README for additional insights
• The app uses MongoDB (MONGODB_URI) and Google OAuth via NextAuth.
• DevSecOps steps:
• Build → Tag → Push Docker image → Update K8s manifests.
• Terraform for EKS & EC2 provisioning.
• ArgoCD for GitOps-driven deployments.
• Jenkins master/agent pipeline with SonarQube, OWASP Dependency-Check and Trivy scans.
• Observability via Prometheus/Grafana.
Essential architectural elements
• Infra provisioning (Terraform → AWS EKS + EC2).
• CI/CD vs GitOps separation.
• How ConfigMap/Secrets feed runtime.
• Monitoring stack as integral to production.
• Don’t over-fragment—group related microservices and pipeline steps logically.