How phunkybob/meeting-minutes works
Project Type and Purpose
• This is a full-stack application where the “frontend” is implemented as a Streamlit dashboard (launched via main.py) and the “backend” encompasses business logic, transcription analysis, and database interactions.
• Key external dependencies include AssemblyAI (for transcription) and LeMUR (for analysis).
File Structure
• Top-level files: main.py serves as the entry point, and configuration files (Dockerfile, docker-compose.yml, .env.sample, pyproject.toml) indicate containerization and dependency management.
• The meeting_minutes directory contains core components:
• database.py: likely handles the SQLite database initialization and session management via SQLAlchemy.
• models.py: defines ORM models for data consistency.
• repository.py: abstracts data access operations.
• services.py: holds business logic or orchestrates operations between transcription, analysis, and storage.
• tab_history.py, tab_new.py, tab_prompts.py, tabs.py: handle different view components in the interactive interface.
• The tests directory verifies that repository and services functions are working as expected.
Elements
• UI to Services (user actions triggering logic).
• Services to Repository and vice versa (for data storage/retrieval).
• Services to External APIs (for transcription and analysis).
• Containerization element (Docker) as an additional layer “wrapping” the application components.