How fneell-byte/server-zip- works
This is a Telegram-connected SMS collection and delivery service. Android-side clients submit SMS batches over HTTP; the server deduplicates them, notifies administrators and workers, and serves saved delivery-note text. Telegram users can create or view delivery notes, while administrators can manage admin status. The graph separates HTTP handling, bot workflows, SQLite state, and Telegram messaging. Source excerpts show the main calls; the SQLite file is identified by the tree, but its schema and contents were not inspected.
Main entry points: database.db Application database · bot.js Bot handlers · index.js HTTP server · telegram.js Message helpers
Components 11
HTTP service
- HTTP server
index.js - SMS ingestion
index.js - Note lookup
index.js
Telegram bot
- Bot handlers
bot.js - Note workflow
bot.js - Admin workflow
bot.js
SQLite state
- Application database
db/database.db
Telegram messaging
- Message helpers
telegram.js
Other components
- SMS client
- Telegram user
- Telegram API
Connections 14
- SMS client → HTTP server: sends requests
index.js - HTTP server → SMS ingestion: routes POST
index.js - HTTP server → Note lookup: routes GET
index.js - SMS ingestion → Application database: checks and saves
index.js - Note lookup → Application database: reads note
index.js - SMS ingestion → Message helpers: sends alerts
index.js - Note lookup → Message helpers: sends logs
index.js - Telegram user → Bot handlers: sends updates
bot.js - Bot handlers → Note workflow: enters workflow
bot.js - Bot handlers → Admin workflow: enters workflow
bot.js - Bot handlers → Application database: reads and writes
bot.js - Note workflow → Application database: saves note
bot.js - Admin workflow → Application database: updates admins
bot.js - Message helpers → Telegram API: posts messages
telegram.js