Scope: 4-source architecture — Splynx, UISP, MikroTik, Zabbix/SNMP with build phases and page-to-source mapping

This commit is contained in:
root
2026-07-25 15:20:32 -04:00
parent 1f3d55d89f
commit 6b8f492b38
2 changed files with 259 additions and 64 deletions
+36 -9
View File
@@ -2,7 +2,42 @@
---
## 2026-07-25 — Project Inception & API Connection
## 2026-07-25 (PM) — Multi-Source Architecture Scoped
**Scope expansion:** The portal at my.forefrontwireless.com will aggregate data from four sources, not just Splynx:
### Data Sources
| Source | Purpose | Auth | Location |
|--------|---------|------|----------|
| **Splynx v4.2** | Billing, CRM, customers, invoices, services | HMAC-SHA256 signature | Self-hosted at portal.forefrontwireless.com |
| **UISP (UNMS)** | Network management, tower/AP inventory, link quality | API token | app2 Docker (unms.forefrontwireless.com) |
| **MikroTik RouterOS** | Real-time bandwidth, DHCP leases, queue stats | REST API or SSH | 5 × CCR2004 routers on network |
| **Zabbix / SNMP** | Infrastructure monitoring, SNMP for non-UISP devices, historical graphs | Zabbix API | Currently on-prem; may move to cloud |
### Architecture Decision
The FastAPI backend is now an **aggregation layer** — read-only adapters for each source, normalizing data into a unified customer view. The backend never writes to Splynx/UISP/MikroTik/Zabbix directly; all mutations stay in the native tools.
### Build Phases
| Phase | Sources | V1? |
|:---:|---|---|
| 1 | Splynx (billing + CRM) | Yes — core self-service |
| 2 | MikroTik (router telemetry) | Yes — data usage, device lists |
| 3 | UISP (network management) | V2 — network status, outage awareness |
| 4 | Zabbix/SNMP (infra monitoring) | V2+ — SLA dashboards, historical graphs |
### Zabbix Migration Options
- **Recommended:** Cloud Zabbix + on-prem proxy — SNMP stays local, server moves to managed infra
- **Alternative:** Keep on-prem, API tunnel via Tailscale — zero cost, simple
- **For later:** Decision deferred until portal reaches Phase 4
### Page-to-Source Mapping
Every customer-facing feature mapped to its backend data provider — see README Data Aggregation Model section.
---
## 2026-07-25 (AM) — Splynx API Connection
**Context:** Germaine shared Splynx API credentials for Forefront Wireless, his WISP company. The self-hosted Splynx instance (v4.2) runs at `portal.forefrontwireless.com/admin/`. The goal is to build a branded customer portal at `my.forefrontwireless.com`.
@@ -37,11 +72,3 @@ Key: 5a8dc490716424f435306f2c18b4fdcb
Secret: 5773f779e5ae5aac965845a66bd857a0
Base: https://portal.forefrontwireless.com/api/2.0/
```
### Next Steps (When Ready)
1. Register `my.forefrontwireless.com` DNS
2. Build FastAPI backend with Splynx proxy layer
3. Build React dashboard
4. Stripe integration for payments
5. Deploy on app3 via CloudPanel