How rashek17/clinica-app works
Project type and purpose
• Clinica-App is a full-stack web application for managing medical appointments, user roles (paciente, médico, administrador), and medical histories.
File structure
• Top-level:
• server.js – Express entrypoint
• package.json / node_modules – backend dependencies
• bd/clinica-app.sql – MySQL schema and seed data
• index.html, css/, js/, view/ – static frontend assets and role-specific views
• tests/ – end-to-end and concurrency tests
• Pattern: classic client–server with static assets served by Express and dynamic data via REST API
README for additional insights
• Tech stack: HTML/CSS/JS/Bootstrap frontend; Node.js/Express backend; MySQL via XAMPP; JWT for auth; bcrypt for password hashing
• Key features mapped to roles and data flows
Elements
• Clear labels: “Paciente Browser,” “Express API,” “MySQL DB,” etc.
• Client → Server (HTTP requests)
• Server → DB (SQL queries)
• DB → Server → Client (JSON responses)
• Blue rectangles for UI components
• Green for backend layers
• Step 1: Sketch all user roles as separate browser nodes.
• Step 5: Overlay authentication flow: login → JWT issuance → token sent in Authorization header.