How bray0829/optica-despliegue works
Project Type and Purpose
• This is a single-page application (SPA) built with React (JSX) and Vite.
• It leverages Supabase for authentication, real-time database (Postgres), and CRUD operations.
• It’s structured as a client-heavy app with no custom server code; all dynamic data interactions go through Supabase’s API.
File Structure
• src/main.jsx + index.html: the SPA entry point.
• src/lib/supabaseClient.js: Supabase initialization module.
• src/context: React Context providers for Auth and Settings.
• src/services: wrappers around Supabase calls for especialistas, examenes, pacientes, usuarios.
• src/Componentes & src/paginas: UI components and routed pages (Login, Dashboard, Citas, Pacientes, Examenes, Remisiones, Juegos, etc.).
• public/_redirects: indicates static hosting (e.g., Netlify) configuration.
• scripts/create-env.ps1: helper to scaffold .env files for VITE_ environment variables.
README Insights
• Confirms React + Vite setup, ESLint rules, plugin usage.
• Describes how to configure Supabase via .env variables.
• Points to src/lib/supabaseClient.js as the locus for CRUD operations.
Main Components and Interactions
a. Frontend (Browser/Client)
• Vite Dev Server (during dev) / CDN + Static Hosting (Netlify, Vercel) in prod.
• index.html → main.jsx bootstraps the React App.
• React App Layers:
• Context Providers (AuthContext, SettingsContext)
• Router (defines AdminRoute, PrivateRoute, public pages)
• Page Components (Dashboard, Citas, Pacientes, etc.)
• Shared Components (Header, Footer, Sidebar, Modals, Alerts)
• src/services invoke methods in supabaseClient.js for data fetch/update.
b. Backend (Supabase)
• Supabase Auth service handles sign-up, log-in, session management.
• Supabase Postgres database stores tables: usuarios, pacientes, examenes, remisiones, citas, especialistas.
• Real-time subscriptions (if used) for live updates on tables.
c. External/Hosting
• Static file hosting (Netlify/Vercel): serves built JS/CSS/assets.
• Environment: VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY passed to client.
Architectural Patterns and Design Principles
• SPA architecture: clear separation of concerns between UI, state management (Context), and services.
• React Context for cross-app state (auth, settings).
• Service layer abstracts direct Supabase calls.
• Component hierarchy: Layout → Sidebar/Header/Footer → Page → Domain components.
• Routing guards via AdminRoute/PrivateRoute.