How undeadnemo/starjet_soc_mbp works
Starjet SOC PC is an Element Plus administration frontend for ERP identity, organization, and access management. The principal workflow is an administrator signing in, then navigating protected routes to manage departments, positions, employees, users, roles/data scopes, permission resources, sessions, audit records, and MFA. The repository also contains finance, materials, and flight-operations screens, which are preserved as product areas. The README identifies Spring Session, Redis, and HttpOnly cookies as the production authentication boundary; backend implementation is not present in this tree. Wiring beyond the sampled entry points and shared client is therefore summarized conservatively.
Main entry points: index.ts Router and guards · admin.ts Admin API · request.ts HTTP client · auth.ts Auth API
Components 17
App Shell
- App entry
apps/web-ele/src/main.ts - Bootstrap
apps/web-ele/src/bootstrap.ts - Router and guards
apps/web-ele/src/router/index.ts
Identity and Access
- Login views
apps/web-ele/src/views/_core/authentication/login.vue - Auth state
apps/web-ele/src/store/auth.ts
Administration Domains
- Identity admin
apps/web-ele/src/views/system/users/index.vue - Organization admin
apps/web-ele/src/views/system/departments/index.vue - Roles and resources
apps/web-ele/src/views/system/roles/index.vue - Security oversight
apps/web-ele/src/views/system/audit/index.vue
ERP Work Areas
- Finance screens
apps/web-ele/src/views/finance/payment-application/index.vue - Materials screens
apps/web-ele/src/views/materials/aviation-materials/index.vue - Flight operations
apps/web-ele/src/views/operations/flight-plan/index.vue
Service Boundary
- Auth API
apps/web-ele/src/api/core/auth.ts - HTTP client
apps/web-ele/src/api/request.ts - Admin API
apps/web-ele/src/api/admin.ts
Other components
- Administrator
- Spring backend
Connections 24
- Administrator → Login views: enters credentials
- App entry → Bootstrap: starts app
- Bootstrap → Router and guards: initializes routing
- Login views → Auth API: requests sign-in
- Auth API → HTTP client: uses client
- HTTP client → Spring backend: sends request
- Spring backend → HTTP client: returns response
- Auth state → Auth API: invokes auth calls
- Router and guards → Auth state: checks access state
- Router and guards → Identity admin: routes to screens
- Router and guards → Organization admin: routes to screens
- Router and guards → Roles and resources: routes to screens
- Router and guards → Security oversight: routes to screens
- Router and guards → Finance screens: routes to screens
- Router and guards → Materials screens: routes to screens
- Router and guards → Flight operations: routes to screens
- Identity admin → Admin API: uses admin API
- Organization admin → Admin API: uses admin API
- Roles and resources → Admin API: uses admin API
- Security oversight → Admin API: uses admin API
- Admin API → HTTP client: uses client
- Finance screens → Admin API: API wiring uncertain
- Materials screens → Admin API: API wiring uncertain
- Flight operations → Admin API: API wiring uncertain