How aakku106/codetracker works
Project type and purpose
• This is a small full-stack web application built in Python (likely using Flask, given the typical file names) whose purpose is to track, display, and periodically update a chronological work log. It uses server-side templates, a simple CSV file as its data store, and a Git repository update mechanism.
File structure
Top-level:
• app.py – main web server application
• update_repo.py – script that pulls changes from a Git repo and updates local logs
• logs.csv – primary data store for work-log entries
• git_update.log – audit of the Git-pull/update operations
• __pycache__ – compiled Python modules (auto-generated)
Directories:
• static/ – static assets (CSS, images, JS)
– style.css
• templates/ – Jinja2 (or Flask) templates for server-side rendering
– index.html (homepage showing latest entries)
– logs.html (detailed listing view)
README for additional insights
• README.md contains only a log table of entries (S.N, function description, timestamp).
• A browser-based UI
• Server logic to read/write logs.csv
• A background or on-demand Git-update process
Detail
• Don’t omit minor but essential pieces: the scheduler, log file, static-asset serving.
• End-to-end flow of a user viewing logs and the background update process.