How devgardencc/reg_service__back works
This is a FastAPI registration service. A client submits registration details; the API validates them, writes a timestamped row to Google Sheets, then schedules a Telegram notification rendered from a Jinja template. It also exposes a health check. Configuration supplies the sheet, Telegram and hosting settings. The graph reflects the inspected route and service code; no database beyond Google Sheets or additional workflow stages are evidenced.
Main entry points: main.py FastAPI routes · service.py Sheets service · logger.py Logger · scheme.py Request schemas
Components 10
API
- FastAPI routes
main.py - Request schemas
app/scheme.py - Telegram template
app/templates/telegram_msg.j2
Integrations
- Sheets service
app/service.py - Telegram service
app/service.py
Other components
- Registration client
- Google Sheets
- Telegram API
Connections 12
- Registration client → FastAPI routes: submits registration
main.py - Registration client → FastAPI routes: checks health
main.py - FastAPI routes → Request schemas: validates and responds
main.py - FastAPI routes → Settings: reads settings
main.py - FastAPI routes → Sheets service: appends row
main.py - Sheets service → Google Sheets: writes row
app/service.py - FastAPI routes → Telegram template: renders message
main.py - FastAPI routes → Telegram service: schedules notification
main.py - Telegram service → Telegram API: sends message
app/service.py - FastAPI routes → Logger: logs events
main.py - Sheets service → Logger: logs errors
app/service.py - Telegram service → Logger: logs outcomes
app/service.py