How raviteja-5976/task-manager-using-streamlit works
Project Type & Purpose
• Full-stack, single-repo Streamlit web application
• Frontend and backend are both in Python, served via Streamlit
• Uses a MySQL relational database to store and manage GDSC task data
• Modular code organized by pages and feature categories (NON-TECHNICAL / TECHNICAL)
File Structure
• Top-level files:
– README.md, LICENSE (project metadata)
– signup.py, member_add.py, member.py, lead_page.py, common_page.py (Streamlit page entry points)
• Gdsc/ directory: houses feature modules by domain:
– NON-TECHNICAL/{marketing, design, management, social media, writing}
– TECHNICAL/{android, cloud, comp code, flutter, machine learning, webdev}
• Each domain has two files:
– *auth.py (authentication & permission checks)
– *.py (main feature logic and UI components)
• __pycache__ directories (compiled bytecode – not part of runtime architecture)
Key Insights from README
• Streamlit app (serves UI over HTTP)
• MySQL database backend
• Core use case: CRUD operations on “tasks” for different GDSC categories
• Intended for college-level GDSC chapter management
Main Components
a. Client Browser / User Agent
b. Streamlit Server (Python runtime)
c. Application Modules:
– Authentication Layer (signup.py, *auth.py modules)
– Page Controllers (lead_page.py, member.py, member_add.py, common_page.py)
– Feature Domains (Marketing, Design, etc.)
d. Database Layer: MySQL server
e. External Dependencies:
– Streamlit library
– mysql-connector / SQLAlchemy (or similar)
– (Optional) Deployment environment (Streamlit Cloud, Docker, etc.)
Relationships & Data Flow
1. User requests a page via browser → HTTP request to Streamlit server
2. Streamlit routing selects the corresponding page controller (e.g., signup.py)
3. Controller calls authentication module (*auth.py) to verify user credentials
4. Upon success, controller invokes feature module logic (e.g., marketing.py)
5. Feature module executes CRUD queries against MySQL via connector
6. MySQL returns data → feature module formats results → Streamlit renders UI
7. User sees updated UI; interactions loop back in the same flow
Architectural Patterns & Principles
• Modular separation: each domain is self-contained (authentication + business logic)
• Page-based MVC-like pattern:
– View: Streamlit UI elements in page scripts
– Controller: page scripts handle user events & coordinate modules
– Model: SQL operations through a DB connector library
• Single codebase deployment, but logically layered
Final Checklist
[ ] All major components clearly labeled
[ ] Key technologies/frameworks noted
[ ] Modular grouping of feature domains (for clarity)