How darshanchaudharii/xeepl_erp works
Project type and purpose
• XEEPL ERP is a full-stack, production-oriented ERP system with two main deliverables:
• A React/Vite-based single-page app (frontend)
• A Spring Boot REST API (backend) backed by JPA/MySQL and a file‐system upload directory for catalogs
• Its core use case is to manage users, sections, contents, items, raw materials, catalogs and quotations (with nested lines and PDF export).
File structure
Top‐level layout:
• “XEEPL ERP Backend” – Spring Boot project (Maven)
– src/main/java/com/xeepl/erp/controller → REST controllers
– src/main/java/com/xeepl/erp/service → business services
– src/main/java/com/xeepl/erp/repository → JPA repositories
– src/main/java/com/xeepl/erp/entity → domain entities
– src/main/java/com/xeepl/erp/dto → data-transfer objects
– config, filter, exception, util packages
– application.properties for DB and file-upload config
– uploads/… (catalog PDFs, images, profiles)
– tests under src/test
• “xeepl-erp-frontend” – Vite + React app
– src/components → UI components organized by feature (auth, catalogs, quotations, etc.)
– src/services → JS modules for HTTP calls to REST API
– src/utils, src/hooks → shared utilities
– public/index.html + vite.config.js + dev proxy to /api → localhost:8080
– Cypress E2E test suite
• package-lock.json, readme.md at root (workspace-level metadata)
README for additional insights
• Architecture section already summarizes:
Browser (React @5173) ← REST → Spring Boot API @8080 ← JDBC → MySQL
+ File system (uploads/) for catalogs
+ Client-side PDF renderer
Detail is key—capture all essential elements
• Do not omit the JWT authentication filter between incoming requests and controllers.
• Client-side PDF utility as part of the UI layer to reflect that PDF export matches web view.