How andybd2703/admininfo works
Project type and purpose
• This is a full-stack, single-page application (SPA) for event management and ticket sales.
• Frontend: Vue.js SPA that handles routing, views, state management (via eventBus), API calls.
• Backend: Node.js + Express REST API, following an MVC-style structure (config, models, controllers, routes, middlewares).
• Database: MySQL for persisting users, events, carts, purchases, favorites.
• File storage: local uploads folder for event images; templating for invoice (HTML).
File structure
• Top level:
• SIDE-frontend/ – Vue.js project (babel.config.js, public/index.html, src/)
• SIDE-backend/ – Express app (index.js, app.js, controllers/, routes/, models/, middlewares/, tests/, uploads/, templates/)
• database/ – SQL script or instructions to create the MySQL schema.
• Backend MVC pattern:
• config/db.js – DB connection
• models/*.js – ORM/schema definitions (Event, User, etc.)
• controllers/*Controller.js – business logic
• routes/*.js – define REST endpoints (/auth, /events, /carrito, /compra, etc.)
• middlewares/auth.js – JWT or session-based protection
• uploads/ – static storage served via Express
• templates/plantillaFactura.html – invoice generation
• Frontend SPA structure:
• src/router/index.js – defines client-side routes (VueRouter)
• src/views/*.vue – pages (home, login, register, event detail, cart, admin dashboards)
• src/services/api.js – Axios wrapper for calling backend endpoints
• src/eventBus.js – simple pub/sub for cross-component comms
README for additional insights
• Confirms RESTful communication, SPA, two user roles (attendee & organizer), MySQL backend.
• No mention of external payment gateway, but controllers/checkoutController.js likely handles payment integration.