How jluse63/2i2d works
This is a bicycle-fall alert platform. A Raspberry Pi reads GPS telemetry, converts coordinates, and submits an alert to the PHP ingestion endpoint, which stores it in the database. An administrator authenticates through the web entry point, views active alerts separated into localized and non-localized cases, optionally opens coordinates in Google Maps, and archives handled alerts. The sampled code confirms GPS ingestion, persistence, authentication, dashboard refresh, and archiving; fall-detection triggering itself is not shown.
Components 15
Device telemetry
- GPS collector
projet/Py/GPS-SERVER.py
Alert backend
- Alert endpoint
projet/pages/add.php - Database connector
projet/admin/log-db.php - Alert database
Admin dashboard
- Web entry
projet/index.php - Alert dashboard
projet/pages/data.php - Localized alerts
projet/pages/data/avec.php - Unlocated alerts
projet/pages/data/sans.php - Archive action
projet/pages/data/archive.php
Access control
- Login page
projet/pages/login.php - Credential check
projet/pages/login/verif-mdp.php - Login session
projet/pages/login/verif-mdp.php
Other components
- GPS sensor
- Administrator
- Google Maps
Connections 17
- GPS sensor → GPS collector: provides NMEA
- GPS collector → Alert endpoint: sends alert
- Alert endpoint → Database connector: uses connection
- Alert endpoint → Alert database: writes alert
- Administrator → Web entry: opens portal
- Web entry → Login page: dispatches login
- Login page → Credential check: submits credentials
- Credential check → Login session: sets session
- Web entry → Login session: checks session
- Web entry → Alert dashboard: loads dashboard
- Alert dashboard → Localized alerts: renders localized
- Alert dashboard → Unlocated alerts: renders unlocated
- Localized alerts → Alert database: reads alerts
- Unlocated alerts → Alert database: reads alerts
- Administrator → Archive action: archives alert
- Archive action → Alert database: updates archive
- Localized alerts → Google Maps: opens coordinates