
Developed automated CI/CD pipelines and infrastructure enhancements for ONDC-Official/automation-mock-service and ONDC-Official/automation-frontend, focusing on reliable deployments to EC2 using Docker Compose and GitHub Actions. Implemented SSH-based cloning, dynamic environment variable management with YAML and Shell scripting, and idempotent deployment workflows that include workspace cleanup and service restart policies. Standardized Docker usage and improved path handling to ensure consistent deployments from the main branch. Adjusted frontend build and serve configurations, including port remapping, to align with updated project structures. These efforts reduced manual intervention, increased deployment reliability, and streamlined backend and frontend rollout processes across environments.
December 2024: Implemented automated CI/CD pipelines and infrastructure improvements across ONDC automation modules, delivering reliable, repeatable deployments to EC2 with Docker Compose and environment secrets management. Backend (automation-mock-service) deployment now SSH-clones, generates .env from secrets, and deploys with Docker Compose, with safeguards including workspace cleanup, docker availability checks, and a restart: always policy. Standardized Docker usage (docker compose), fixed path handling, and branch alignment to main. Frontend (automation-frontend) CI/CD now deploys both UI and backend from the main branch to EC2, with portfolio of configuration refinements and a port/build-serve alignment to the new project structure. Technologies and practices demonstrated include GitHub Actions-based pipelines, Docker and Docker Compose, SSH-based deployments, environment variable management, port and path remapping, and idempotent, safety-first deployment workflows.
December 2024: Implemented automated CI/CD pipelines and infrastructure improvements across ONDC automation modules, delivering reliable, repeatable deployments to EC2 with Docker Compose and environment secrets management. Backend (automation-mock-service) deployment now SSH-clones, generates .env from secrets, and deploys with Docker Compose, with safeguards including workspace cleanup, docker availability checks, and a restart: always policy. Standardized Docker usage (docker compose), fixed path handling, and branch alignment to main. Frontend (automation-frontend) CI/CD now deploys both UI and backend from the main branch to EC2, with portfolio of configuration refinements and a port/build-serve alignment to the new project structure. Technologies and practices demonstrated include GitHub Actions-based pipelines, Docker and Docker Compose, SSH-based deployments, environment variable management, port and path remapping, and idempotent, safety-first deployment workflows.

Overview of all repositories you've contributed to across your timeline