How anasrawuthar-bit/gibilling works
ZynBill is an offline-capable desktop billing and accounting product with a companion multi-tenant cloud service. The principal runtime centers on the Electron application, which uses the local database for business operations and also coordinates synchronization and WhatsApp features. The cloud server handles customer accounts and related services; sync transfers events between the desktop database and its HTTP API. Database migration and integrity diagnostics form an important internal layer. The README is empty, and the sampled excerpts do not show renderer workflows or all business capabilities, so those relationships are not inferred.
Main entry points: server.js Cloud API Server · main.js Desktop Application · sync-service.js Sync Service · database.js Business Database
Components 16
Desktop Runtime
- Desktop Application
main.js - Cloud Client
cloud-desktop-client.js - Sync Service
sync-service.js - WhatsApp Service
whatsapp-service.js
Accounting Data
- Business Database
database.js - Schema Migrations
database-migrations.js - Integrity Dry Run
data-integrity-dry-run.js - Database Diagnostics
database-diagnostic-core.js - Migration Readiness
migration-readiness.js
Cloud Service
- Cloud API Server
server/server.js - Cloud Database
server/db.js - Environment Config
server/env-loader.js - Email Service
server/smtp.js - Backup Encryption
server/backup-crypto.js
External Integrations
- Sync HTTP API
sync-service.js - WhatsApp Network
Connections 15
- Desktop Application → Business Database: uses
main.js - Desktop Application → Sync Service: starts
main.js - Desktop Application → WhatsApp Service: uses
main.js - Business Database → Schema Migrations: runs
database.js - Database Diagnostics → Integrity Dry Run: checks
database-diagnostic-core.js - Migration Readiness → Integrity Dry Run: uses
migration-readiness.js - Sync Service → Business Database: claims events
sync-service.js - Sync Service → Sync HTTP API: pushes and pulls
sync-service.js - WhatsApp Service → WhatsApp Network: sends messages
- Cloud API Server → Environment Config: loads
server/server.js - Cloud API Server → Cloud Database: uses
server/server.js - Cloud API Server → Email Service: uses
server/server.js - Cloud API Server → Backup Encryption: uses
server/server.js - Cloud Database → Environment Config: loads
server/db.js - Email Service → Cloud Database: uses
server/smtp.js