How marcojaycee2-afk/wifi works
NAPBOX is an ISP customer and network-access-point manager. An administrator signs in, manages the client roster and NAP boxes, and connects clients to available ports; the application stores shared state in PostgreSQL. The NAP interface also provides grid, splitter, and map views. The sampled server and NAP excerpts support the authentication, persistence, and map-configuration links shown; the README documents the client workflow and map providers, but much of the general dashboard implementation was not sampled.
Main entry points: server.js HTTP API · naps.js NAP boxes and ports · login.html Sign-in page · index.html Management dashboard
Components 9
Admin access
- Sign-in page
login.html - Session authentication
backend/auth.js
ISP management
- Management dashboard
index.html - NAP boxes and ports
naps.js
Application service
- HTTP API
backend/server.js - Saved application state
backend/schema.sql
Mapping
- OpenStreetMap tiles
- Mapbox maps
Other components
- Administrator
Connections 10
- Administrator → Sign-in page: signs in
README.md - Sign-in page → HTTP API: submits credentials
backend/server.js - HTTP API → Session authentication: checks sessions
backend/server.js - HTTP API → Sign-in page: serves page
backend/server.js - HTTP API → Management dashboard: serves dashboard
backend/server.js - Management dashboard → HTTP API: loads and saves state
README.md - HTTP API → Saved application state: reads and writes
backend/server.js - NAP boxes and ports → HTTP API: fetches map config
naps.js - NAP boxes and ports → OpenStreetMap tiles: uses fallback tiles
README.md - NAP boxes and ports → Mapbox maps: optionally renders map
naps.js