How mehuljain2003/chiru2 works
Project type and purpose
• This is a single‐service Python backend application (no separate frontend) packaged for Heroku (docker/heroku.yml/Procfile present) whose job is to fetch and process video information (see get_video_info.py, subscription_data.txt).
• It exposes HTTP endpoints (likely via app.py) and/or can be invoked as a CLI (main.py, p_bar.py).
File structure
• Top level:
• Dockerfile, heroku.yml, Procfile: deployment and runtime descriptions
• runtime.txt, requirements.txt: Python runtime & dependencies
• app.py: HTTP entry point
• main.py + helper.py + get_video_info.py + p_bar.py: business logic modules
• config.py: environment/config management
• logger.py: logging abstraction
• subscription_data.txt: lightweight storage for subscriptions
• No separate “frontend” or database directory: this is a single‐service API tool.
README
• Only a “Deploy to Heroku” button—no further architectural details provided.
Detail
• Every Python module as a sub‐component of the app
• Config.py feeding settings into all modules
• Where and how subscription_data.txt is accessed
• Logging pipeline to Heroku Logs
• Don’t omit even small utilities (p_bar.py) – these are part of your service boundary