How abelheddy/simplepos works
Project type and purpose
• This is a full-stack Point of Sale (SimplePos) application, consisting of:
• A React/Vite-based frontend
• Two alternative backend implementations (one in Go, one in Node.js)
• A database layer for storing users, roles, products, sales, etc.
File structure
• Top level:
• Backend/
– go/ (Go REST API: database init, handlers, middleware, models)
– node/ (Node.js Express API: controllers, models, routes, db.js)
• Frontend/ (React app under src/, uses Vite, Tailwind, React Router, Context API)
• Productos.sql (initial product data script)
• Backend/go follows a layered pattern (models → handlers → main), uses environment config, middleware for auth.
• Backend/node follows MVC (models ↔ controllers ↔ routes), with connection logic in src/db.js.
• Frontend uses component hierarchy and React contexts for authentication and role-based routing.
Pulling insights from the README
• The project is named SimplePos