How zahar-pr/speech-analytics works
Project type and purpose
• This is a two-part, full-stack integration application:
a. A C#/.NET 9.0 “front” component that likely hosts a minimal Web API or UI.
b. A Python-based “amo-integration” service that orchestrates calls to external systems (amoCRM, GigaChat, PBX, SberSpeech).
• Purpose: accept requests from the Frontend, transform and route them to external services via dedicated Python service modules, then return or log the combined response.
File structure
• Top level:
• README.md (empty)
• amo-integration/
• front/
• logs/
• amo-integration/:
• main.py – entry point for orchestration logic
• conf/ – prompt templates and certificates (russian.pem)
• models/ – Pydantic or domain models for each external system (amo.py, gigachat.py, pbx.py, speech.py)
• services/ – connectors/clients for each external system (amo.py, gigachat.py, pbx.py, sberspeech.py)
• utils/ – common utilities (e.g., logging setup)
• requirements.txt – Python dependencies
• front/:
• front.sln & front.csproj – .NET solution and project files targeting .NET 9.0
• Program.cs – minimal-API host configuration
• appsettings.json(+Development) – configuration for the .NET app
• logs/: centralized file logs.log capturing runtime events
(empty) README
• No explicit architecture section; rely on directory naming and file roles to infer layers and data flows.