How nicolasantoniosilvaruiz-cmyk/fundosancarlosapi works
San Carlos monitors water-tank levels and petroleum inventory through a Django service and Android client. The main workflow is Android sign-in and panel requests to the mobile API, which reads tank measurements and returns status; low-water evaluation creates alerts and can trigger browser or Android notifications. The app also exposes administration and petroleum operations. Edges reflect shown calls, indexed references, or documented API behavior; unsampled web routing and some integrations are left unconnected where their wiring is not evidenced.
Main entry points: models.py Domain records · services.py Level evaluation · MainActivity.java Mobile screens · api_movil.py Mobile API
Components 20
Android client
- Mobile screens
android/app/src/main/java/cl/fundosancarlos/app/MainActivity.java - HTTP client
android/app/src/main/java/cl/fundosancarlos/app/Api.java - Local session/cache
android/app/src/main/java/cl/fundosancarlos/app/LocalStore.java - Push handling
android/app/src/main/java/cl/fundosancarlos/app/PushAndroid.java - FCM receiver
android/app/src/main/java/cl/fundosancarlos/app/WaterMessagingService.java
Service APIs
- Mobile API
django/monitoreo/api_movil.py - Water API
django/monitoreo/api_agua.py - Web views
django/monitoreo/views.py - Management API
django/monitoreo/gestion_api.py - Runtime settings
django/config/settings.py
Monitoring domain
- Domain records
django/monitoreo/models.py - Level evaluation
django/monitoreo/services.py
Administration
- Employee forms
django/monitoreo/gestion_forms.py - Admin operations
django/monitoreo/gestion_services.py - Web forms
django/monitoreo/forms.py
Notifications
- Browser push
django/monitoreo/push.py - Android push sender
django/monitoreo/fcm.py
Other components
- Operator
- Water device
- Push provider
Connections 30
- Operator → Mobile screens: uses
- Mobile screens → HTTP client: requests through
android/app/src/main/java/cl/fundosancarlos/app/MainActivity.java - Mobile screens → Local session/cache: stores session
android/app/src/main/java/cl/fundosancarlos/app/MainActivity.java - Mobile screens → Push handling: configures push
android/app/src/main/java/cl/fundosancarlos/app/MainActivity.java - HTTP client → Mobile API: calls API
android/app/src/main/java/cl/fundosancarlos/app/Api.java - Water device → Water API: submits readings
- Mobile API → Water API: references
django/monitoreo/api_movil.py - Water API → Domain records: reads and writes
django/monitoreo/api_agua.py - Water API → Level evaluation: uses status services
django/monitoreo/api_agua.py - Mobile API → Domain records: reads and writes
django/monitoreo/api_movil.py - Mobile API → Level evaluation: uses status services
django/monitoreo/api_movil.py - Level evaluation → Domain records: evaluates readings
django/monitoreo/services.py - Level evaluation → Browser push: schedules alert notice
django/monitoreo/services.py - Level evaluation → Android push sender: schedules alert notice
django/monitoreo/services.py - Browser push → Domain records: reads subscriptions
django/monitoreo/push.py - Android push sender → Domain records: references records
django/monitoreo/api_movil.py - Browser push → Push provider: sends notice
django/monitoreo/push.py - Android push sender → Push provider: sends notice
- FCM receiver → Local session/cache: checks preferences
android/app/src/main/java/cl/fundosancarlos/app/WaterMessagingService.java - FCM receiver → Push handling: displays notice
android/app/src/main/java/cl/fundosancarlos/app/WaterMessagingService.java - FCM receiver → HTTP client: registers token
android/app/src/main/java/cl/fundosancarlos/app/WaterMessagingService.java - Operator → Web views: uses
- Web views → Web forms: uses forms
django/monitoreo/views.py - Web views → Admin operations: calls operations
django/monitoreo/views.py - Management API → Admin operations: calls operations
django/monitoreo/gestion_api.py - Management API → Employee forms: references forms
django/monitoreo/gestion_api.py - Admin operations → Employee forms: validates employees
django/monitoreo/gestion_services.py - Admin operations → Domain records: updates records
django/monitoreo/gestion_services.py - Management API → Domain records: references records
django/monitoreo/gestion_api.py - Runtime settings → Domain records: configures user model
django/config/settings.py