How atharva2884/devops works
Project type and purpose
• This is a small full‑stack web application built with Flask (Python), serving a simple UI (two HTML pages in templates/ and a CSS file in static/), persisting feedback data in a SQLite database (feedback.db), and packaged for containerized deployment. It includes a minimal CI/CD setup via Jenkinsfile and is composable via docker-compose.yml.
File structure
• Top‑level files:
• app.py: the Flask application entry point, defines routes for / (index) and /dashboard.
• requirements.txt: Python dependencies
• feedback.db, feedback_export.csv: SQLite data store and export snapshot
• Dockerfile, docker-compose.yml: container build and orchestration
• Jenkinsfile: CI/CD pipeline definition
• test_app.py: unit tests for Flask routes
• Directories:
• templates/: Jinja2 HTML templates
• static/: CSS and other static assets
(empty) README for additional insights
• Since the README is blank, we infer architecture solely from the file layout: a monolithic Flask service that renders both the frontend and backend, reading/writing to a SQLite file, deployed in a Docker container, validated by unit tests in Jenkins, and optionally composed via Docker Compose.
• “Static Server” → serves /static/style.css
• “Template Renderer” → uses templates/index.html and dashboard.html