How cine-verse/erpc-front works
Project type and purpose
• This is a full-stack single-page application (SPA) built with Vue 3 and Vite on the frontend and a minimal Node/Express server (server.js) to serve the static build (and potentially proxy API calls).
• The app appears to be an “ERP-style” administrative dashboard (“erpc”) with modules for approvals, contracts, customers, estimates, orders, billing, performance, logistics, notices, sales opportunities, and employee management.
• Deployment targets AWS Elastic Beanstalk (see .ebextensions and Procfile) and uses GitHub Actions (/.github/workflows/deploy.yml) for CI/CD.
File structure
• Top-level:
• package.json, vite.config.js, jsconfig.json: npm scripts, Vite config, JS paths
• server.js: Express server to serve the SPA (and possibly API proxy)
• Procfile/.ebextensions: Elastic Beanstalk deployment config
• .github/workflows/deploy.yml: CI/CD pipeline
• index.html & public/: public assets
• src/: Vue app source
• src/ substructure:
• main.js & App.vue: root of the Vue app
• router/mainRouter.js: client-side routing (SPA)
• components/: feature-based UI modules (approval, contract, customer, etc.)
• assets/css & assets/img: static styles and images
• No direct database or service-layer code, implying that either:
• server.js contains API endpoints, or
README for additional insights
• Confirms usage of Vue 3 + Vite.
• Standard npm “dev” and “build” scripts.