How aqibhafeez473/django-todo-cicd works
Project type and purpose
• This is a full-stack, monolithic Django “todo” web application with built-in templating for the UI and a simple persistence layer (SQLite in dev, with Kubernetes manifests for a MySQL alternative in prod). It is containerized via Docker, orchestrated via Docker-Compose locally and Kubernetes in production, and includes CI/CD pipelines (GitHub Actions + Jenkinsfiles).
File structure
• Top-level:
• Dockerfile, docker-compose.yml, .dockerignore – container build
• Jenkinsfile* – multiple CI/CD pipeline definitions
• .github/workflows/docker-build.yml – GitHub Actions CI
• k8s/ – Kubernetes manifests (deployments, services, configMap, secret for MySQL)
• volume/ – host volume mapping for persistent SQLite data
• manage.py & db.sqlite3 – Django project entry and dev database
• staticfiles/ – compiled static assets (CSS)
• Django project:
• todoApp/ – core project config (settings, URLs, WSGI)
• todos/ – app module (models, views, URLs, templates, migrations, admin)
README
• Confirms it’s a simple Django ToDo app, uses SQLite by default, and instructions to run migrations, create superuser, start dev server on 127.0.0.1:8000/todos.