How verticalpartsia/asset-manager works
Asset Manager is an internal equipment and IT-support portal. Staff use the web app to manage assets, allocations, inventory, support tickets, checklists, and audit/reporting; the README documents Supabase as its backend. The sampled integration implements SSO and hybrid persistence, while the sampled domain modules provide UID and SLA rules. The main UI is represented by the existing public/index.html; its contents were not sampled, so detailed UI-to-backend calls and several documented features cannot be verified here.
Main entry points: index.html Asset Manager UI · vp-integration.js SSO and sync · server.js Static web server · uid.js UID rules
Components 13
Portal workflows
- Asset Manager UI
public/index.html - Asset management
public/index.html - Allocations and returns
public/index.html - Supply inventory
public/index.html - Support and knowledge
public/index.html - Care checklists
public/index.html - Reports and audit
public/index.html
Identity and data
- SSO and sync
public/vp-integration.js - Supabase services
- Static web server
server.js
Other components
- Portal users
Connections 12
- Portal users → Asset Manager UI: uses
README.md - Asset Manager UI → Asset management: manages
README.md - Asset Manager UI → Allocations and returns: assigns
README.md - Asset Manager UI → Supply inventory: tracks
README.md - Asset Manager UI → Support and knowledge: handles
README.md - Asset Manager UI → Care checklists: confirms
README.md - Asset Manager UI → Reports and audit: reports
README.md - Asset management → UID rules: generates UIDs
public/js/domain/uid.js - Support and knowledge → SLA rules: classifies SLA
public/js/domain/sla.js - Portal users → SSO and sync: presents SSO token
public/vp-integration.js - SSO and sync → Supabase services: authenticates and syncs
public/vp-integration.js - Static web server → Asset Manager UI: serves
server.js