How yannhallage/server-client works
Project type and purpose
• This is a full-stack client-server web application.
• The README confirms it follows the classic “client requests data, server responds” model.
• The client is a React (Vite) front-end with UI components and API hooks; the server is a Node/Express back-end exposing REST endpoints and interacting with a database.
File structure
• Top-level folders:
• client/ – React application
• server/ – Node/Express API
• client/ contains:
• src/api – API wrappers (api_post.jsx)
• src/components/ui – Reusable UI primitives (button, dialog, toast, etc.)
• src/context, src/hooks – State and side-effect management (apiContext, use-toast)
• myComponents – Demo or feature components using the UI library
• build/config files (vite.config.js, tsconfig.json, tailwind.config.js)
• server/ contains:
• config/db.js – Database connection setup
• models/ – Data schemas (account, personnel, notifications)
• controllers/ – Business logic for each resource
• routes/ – Express routers binding controllers to endpoints
• app.js/server.js – Express app initialization and server startup
README for additional insights
• The README simply states the client-server paradigm.