How hispanotech-ugc/hispanotech-ugc-web works
Project type and purpose
• HispanoTech-UGC-WEB is a full-stack, static-hosted web application (GitHub Pages) that uses Supabase (PostgreSQL + Auth + Storage + Realtime) as its backend.
• It provides a UI for law-enforcement crisis management (login/registration, operator dashboard, reporting, mapping, robot control) and includes an auxiliary Python script for weapon detection (armas/detectarArmas.py).
File structure
• Top-level “html/”, “css/”, “js/” directories → pure frontend: HTML pages, CSS styles, vanilla JS logic.
• “models/” → client-side data models (users, roles, eventos, informes, robots).
• “services/” → wrappers around Supabase client for auth, admin, operator, user, informs.
• “config/” → DB schema (hispanodb.sql) + Supabase client initialization (supabaseClient.js).
• “armas/” → Python script for weapon detection (external microservice or local batch job).
• “test/” and “doc/” → testing and documentation artifacts.
README for additional insights
• Confirms static-hosted SPA pages (landing, login, registro, operador, admin).
• Emphasizes Supabase Auth, real-time subscriptions, and database schema.
Essential details
• Authentication flow: Browser → Supabase Auth → DB
• Data-CRUD flow: Browser → services/*.js → Supabase Postgres
• Storage flow: Browser → Supabase Storage → Browser
• Realtime updates: Supabase Realtime → Browser
• Python detection: Storage → Weapon Detection Service → Storage/DB