How duarteocarmo/governosombra works
Core Application Components
• Main Application Service (Rust-based)
• Transcript Processing Engine
• Template Rendering System
• Model Management System
Storage Components
• Episodes Directory Storage
• Transcripts Directory Storage
• GGML Model Storage (indicated by download-ggml-model.sh)
External Dependencies
• Docker Container Runtime
• GGML Model Source
Component Relationships
• Model Download Flow: GGML Source → Model Storage → Application
• Processing Flow: Episodes → Rust Core → Transcripts
• Template Rendering: Templates → Rust Core → Generated Output
• Container Architecture: Docker → Application Components
Specific Implementation Details
• Relationship between src/main.rs and src/process.rs
• Template processing for three HTML templates (index, books, episode)
• Containerized nature of the application
Technical Stack Indicators
• Rust Runtime
• GGML Model Integration
• HTML Template Engine
• Docker/Docker Compose Infrastructure
[External Dependencies] → [Core Application] → [Storage]
• ↑ ↑ ↑
• [Docker Infrastructure] [Templates] [Processed Data]
Data processing pipeline
• Input: Episodes
• Processing: Rust Core (process.rs)
• Output: Transcripts
Containerization layer
• Docker container boundary
• Docker Compose service definition
• Volume mappings for persistent storage
Template Processing
• HTML template files
• Template engine integration
• Output generation flow
Model Management
• GGML model download process
• Model storage location
• Model integration with processing engine
• Application logic (src/)
• Data storage (episodes/, transcripts/)
• Presentation layer (templates/)
• Infrastructure (Docker)
This will provide a clear understanding of how the system processes transcripts, manages templates, and handles data flow while maintaining a containerized environment.