How miladraza123/accounting-system works
OHT is a browser-based accounting application with billing, daily-ledger, and master-data pages, backed by Supabase. Its separate scheduled backup job fetches accounting data, produces Excel and restore-file attachments, and emails them. The service worker caches static application files while leaving API requests on the network. The README is empty and most page and SQL sources were not sampled, so UI-to-database wiring and quotation behavior are shown only where supported by the tree or excerpts.
Main entry points: backup.js Backup runner · sw.js Service worker · index.html App entry · daily-backup.yml Scheduled workflow
Components 17
Accounting app
- App entry
index.html - Master data
masters.html - Billing
billing.html - Daily ledger
daily-ledger.html - Service quotations
service-quotations.sql
Offline shell
- Service worker
sw.js - Static shell files
- Browser cache
Daily backup
- Scheduled workflow
.github/workflows/daily-backup.yml - Backup runner
backup-job/backup.js - Accounting tables
- Excel workbook
- Restore package
External services
- Supabase
- Email delivery
Other components
- Accounting user
- Backup recipient
Connections 15
- Accounting user → App entry: opens app
- Accounting user → Master data: manages data
- Accounting user → Billing: creates bills
- Accounting user → Daily ledger: views ledger
- App entry → Service worker: registers worker
- Service worker → Static shell files: caches static files
- Service worker → Browser cache: reads and writes
- Service worker → Supabase: leaves API uncached
- Scheduled workflow → Backup runner: runs daily
- Backup runner → Supabase: signs in and fetches
- Supabase → Accounting tables: returns table data
- Backup runner → Excel workbook: builds workbook
- Backup runner → Restore package: builds restore data
- Backup runner → Email delivery: sends attachments
- Email delivery → Backup recipient: delivers email