⚙️ E-Ticket Backend Infrastructure (Config)

This repository serves as the DevOps Control Plane for the E-Ticket Backend. By decoupling the deployment logic from the core Laravel API, we ensure environment consistency, enhanced security, and rapid scalability across development, staging, and production.

---

🏗️ Deployment Architecture

This configuration suite manages the entire lifecycle of the backend microservice:

• Containerization: Optimized Dockerfiles using multi-stage builds to keep production images lean and secure.
• Orchestration:
  • docker-compose.yml for local development and testing.
  • Kubernetes (K8s) manifests for high-availability production clusters.
• CI/CD Automation: Declarative Jenkins Pipelines that automate testing, security scanning, and automated deployment.
• Monitoring: Integrated health checks and Google Chat webhook notifications for real-time pipeline status.

---

🛠️ Infrastructure Stack

• Orchestration: Docker, Kubernetes
• CI/CD: Jenkins (Groovy)
• Web Server: Nginx (Optimized for Laravel)
• Environment: Dotenv management & Secret handling

---

📂 Repository Structure

Component	Description
/docker	Service-specific Dockerfiles and Nginx configurations.
/k8s	Kubernetes Deployments, Services, and Ingress manifests.
/jenkins	Jenkinsfile defining the automated build and deploy stages.
/scripts	Automation scripts for environment setup and DB migrations.

---

🚀 Usage

Local Development

To spin up the backend environment locally:

git clone [https://github.com/shashidas95/eticket-be-config.git](https://github.com/shashidas95/eticket-be-config.git)
cd eticket-be-config
docker-compose up -d

CI/CD Integration

This repository should be linked as a "Pipeline Script from SCM" in Jenkins to manage the eticket-be deployment lifecycle.

---

👨‍💻 Author

Shashi Kanta Das Software Architect | DevOps Engineer | Assistant Director @ BSTI