e2e-devops

What This Project Demonstrates

Fully automated CI/CD — push to deploy, no manual steps

Production-style HTTPS with real end-to-end encryption

Self-hosted infrastructure, from Git to cloud VM

Secrets kept out of source control by design

Architecture

CI/CD Deployment Flow

Developer (VS Code)
      │  git push
      ▼
Forgejo (self-hosted Git server)
      │  triggers workflow
      ▼
Forgejo Runner (Docker-based)
      │  rsync over SSH
      ▼
Oracle Cloud VM
      │  docker compose up --build
      ▼
Nginx container (HTTPS)

Network Traffic Flow

End User
      │  HTTPS request
      ▼
Cloudflare (DNS + Universal SSL + CDN)
      │  Full (strict) — encrypted to origin
      ▼
Nginx on OCI VM (real SSL cert)
      │
      ▼
Static Web App

Tech Stack

Version Control	Forgejo (self-hosted)
CI/CD	Forgejo Actions + Docker-based Runner
Containers	Docker & Docker Compose
Cloud	Oracle Cloud Infrastructure (OCI)
DNS / Security	Cloudflare (DNS, WAF, Universal SSL)
Web Server	Nginx (TLS termination)
OS	Ubuntu Server

Key Engineering Decisions

Chose SSH + rsync over a container registry — simpler at this scale, no registry to maintain.
Split rsync into two commands so --delete cleans stale app files without ever touching the SSL certs folder on the server.
Used a Cloudflare Origin Certificate for Full (strict) SSL — real encryption on every hop, not just browser-to-Cloudflare.
Replaced docker compose down && up with up -d --build --remove-orphans to remove the downtime gap on every deploy.
Injected build metadata (commit, build number, deploy time) at CI time via sed, so the live page always reflects exactly what's running.

What's Next

Spring Boot REST API
Database integration
Self-hosted mail server (learning project)
Monitoring, logging, backups
Infrastructure as Code, Kubernetes, GitOps

Version	v0.1.0
Environment	OCI
Commit	46caf95
Build	17
Deployed	07 July 2026, 09:11 AM (IST)