How dzakywifinet-lgtm/dzw-monitoring-sales works
This is a MikroTik voucher-sales and usage dashboard. The main flow is router credentials at login, then dashboard polling and on-demand voucher/PPPoE operations; settings configure quota, notifications, and cron. The graph also preserves sales, bandwidth/traffic, usage analysis, voucher printing, and PWA capabilities described by the README. Most endpoint-to-frontend wiring and several subsystems are documented but not sampled, so those links are dashed and marked unverified rather than inferred as confirmed calls.
Main entry points: functions.php Router and domain logic · auth.php Session auth · index.php Dashboard view · app.js Dashboard browser app
Components 20
Access & Dashboard
- Router login
login.php - Session auth
includes/auth.php - Dashboard view
index.php - Dashboard browser app
assets/app.js
Router Operations
- RouterOS API
lib/routeros_api.class.php - Router and domain logic
includes/functions.php - PPPoE actions
api/pppoe.php - Voucher actions
api/vouchers.php
Usage & Sales
- Live status API
api/live.php - Sales API
api/sales.php - Live traffic API
api/traffic.php - Router usage categories
usage-kategori-mikrotik.rsc
Settings & Storage
- Dashboard settings
settings.php - Print templates API
api/voucher_templates.php - Local JSON state
includes/storage.php
Notifications & PWA
- Scheduled checks
cron.php - Telegram notifications
- Offline app shell
service-worker.js
Other components
- Dashboard user
- MikroTik router
Connections 33
- Dashboard user → Router login: enters credentials
README.md - Router login → Router and domain logic: tests and connects
login.php - Router login → Session auth: stores session
login.php - Session auth → Router and domain logic: connects session
includes/auth.php - Router and domain logic → RouterOS API: uses API client
includes/functions.php - RouterOS API → MikroTik router: sends RouterOS commands
lib/routeros_api.class.php - Dashboard user → Dashboard view: opens dashboard
README.md - Dashboard view → Session auth: requires login
index.php - Dashboard view → Router and domain logic: builds dashboard data
index.php - Dashboard view → Dashboard browser app: loads browser app
- Dashboard browser app → Live status API: polls status
- Dashboard browser app → Sales API: refreshes sales
- Dashboard browser app → Live traffic API: polls bandwidth
- Live status API → Session auth: checks session
api/live.php - Live status API → Router and domain logic: fetches live data
api/live.php - Sales API → Router and domain logic: builds sales data
api/sales.php - Live traffic API → Router and domain logic: fetches interface rate
api/traffic.php - Dashboard user → PPPoE actions: requests PPPoE actions
- PPPoE actions → Session auth: checks session
api/pppoe.php - PPPoE actions → Router and domain logic: runs PPPoE actions
api/pppoe.php - Dashboard user → Voucher actions: manages vouchers
- Voucher actions → Router and domain logic: runs voucher actions
api/vouchers.php - Dashboard user → Print templates API: edits print layouts
- Print templates API → Local JSON state: reads and writes templates
api/voucher_templates.php - Dashboard user → Dashboard settings: configures dashboard
README.md - Dashboard settings → Session auth: requires login
settings.php - Dashboard settings → Local JSON state: saves settings and cron credentials
settings.php - Router and domain logic → Local JSON state: tracks usage state
includes/functions.php - Scheduled checks → Local JSON state: loads cron credentials
cron.php - Scheduled checks → Router and domain logic: runs scheduled checks
cron.php - Scheduled checks → Telegram notifications: sends alerts
- Router and domain logic → Router usage categories: reads router counters
- Dashboard view → Offline app shell: registers service worker
index.php