How alekseyshgit/isimui works
Project type and purpose
• From the file tree and README, this is a full‐stack web application scaffolded with Vue 3 and Vite for the frontend, plus a Node.js “server.js” at the root that bundles and serves the SPA (and provides server‐side APIs or proxying).
• The presence of scripts like install-service.js, ecosystem.config.js, and offline/minimal packaging directories indicates this app is designed to be packaged (online or offline) and run as a service (PM2 or Windows Service).
File structure
• Top‐level “src/” holds the Vue 3 SPA:
• src/main.js, src/App.vue, src/components, src/views, src/router → client UI, routing, component tree.
• src/services & nested api/auth/util directories → client‐side service wrappers for REST or external ISIM APIs.
• “public/index.html” is the single‐page application entry point.
• “server.js” at root launches an HTTP server (likely Express) to serve static built assets and may expose custom server APIs.
• “minimal-package/” and “offline-package/” are pre‐built bundles plus scripts for installing as a local service.
• Config files: vite.config.js, ecosystem.config.js, package.json / package-lock.json.
Key insights from README
• Minimal default text: it’s a Vue 3 + Vite template, so the architecture is client‐heavy SPA.
Detailed callout of components
• Frontend:
• src/main.js (bootstraps app)
• src/router/index.js (client routing)
• src/views/*.vue (page views: LoginView, MainView)
• src/components/*.vue (UI widgets)
• src/services/* (client API wrappers)
• Backend:
• server.js (Express static + API)
• install-service.js / uninstall-service.js (service lifecycle)
• ecosystem.config.js (PM2 cluster config)
• Packaging:
• minimal-package/server.js + start.js
• offline-package/install-service.js + server.js + package.json