How jyothi324/uii works
This tree contains three independent Go backends: delivery tracking, inventory operations, and lead/job management with billing. The principal workflows are HTTP request routing into domain handlers and persistence; delivery also exposes live tracking, while inventory relays activity over WebSockets and lead management includes AI and subscription billing. Edges are limited to registrations and calls visible in the excerpts; several substantial domain modules are represented without inferred internal call chains.
Main entry points: cmd/main.go HTTP server · routes/routes.go API routes · cmd/main.go HTTP routes · routes/routes.go API routes
Components 28
Delivery tracking
- HTTP routes
geo-backend-develop/cmd/main.go - Task handlers
geo-backend-develop/cmd/handlers.go - Geo services
geo-backend-develop/cmd/services.go - Realtime hub
geo-backend-develop/cmd/hub.go
Inventory operations
- HTTP server
inventory-develop/cmd/main.go - API routes
inventory-develop/routes/routes.go - Materials and chunks
inventory-develop/handlers/material.handler.go - Purchasing
inventory-develop/handlers/purchase.handler.go - Purchase receiving
inventory-develop/handlers/purchaserecived.handler.go - Customer visualizer
inventory-develop/handlers/visualizecustomer.handler.go - Audit activity
inventory-develop/handlers/audit_handler.go - Tenant database
inventory-develop/db/connection.go - Activity listener
inventory-develop/internal/postgreslistener/listener.go - Activity WebSockets
inventory-develop/internal/websocket/manager.go
Lead management
- HTTP server
lead-services-develop/cmd/main.go - API routes
lead-services-develop/routes/routes.go - Lead lifecycle
lead-services-develop/handlers/lead.handler.go - Estimates
lead-services-develop/handlers/estimate.handler.go - Estimate stages
lead-services-develop/handlers/estimateStages.handler.go - Stage operations
lead-services-develop/handlers/stage.handler.go - User management
lead-services-develop/handlers/user_handler.go - Job synchronization
lead-services-develop/services/job_service.go - AI assistance
lead-services-develop/services/gemini_service.go - Billing endpoints
lead-services-develop/billing/handler.go - Billing and Stripe
lead-services-develop/billing/service.go
Other components
- API client
- API client
- API client
Connections 18
- API client → HTTP routes: sends requests
geo-backend-develop/cmd/main.go - HTTP routes → Task handlers: routes task requests
geo-backend-develop/cmd/main.go - HTTP routes → Realtime hub: starts hub
geo-backend-develop/cmd/main.go - HTTP routes → Realtime hub: routes WebSockets
geo-backend-develop/cmd/main.go - API client → HTTP server: sends requests
inventory-develop/cmd/main.go - HTTP server → API routes: registers routes
inventory-develop/cmd/main.go - API routes → Materials and chunks: routes material requests
inventory-develop/routes/routes.go - API routes → Purchasing: routes purchases
inventory-develop/routes/routes.go - API routes → Purchase receiving: routes receipts
inventory-develop/routes/routes.go - API routes → Customer visualizer: routes customer requests
inventory-develop/routes/routes.go - HTTP server → Tenant database: initializes manager
inventory-develop/cmd/main.go - HTTP server → Activity listener: starts listener
inventory-develop/cmd/main.go - HTTP server → Activity WebSockets: serves activity sockets
inventory-develop/cmd/main.go - API client → HTTP server: sends requests
lead-services-develop/cmd/main.go - HTTP server → API routes: registers routes
lead-services-develop/cmd/main.go - API routes → Lead lifecycle: routes lead requests
lead-services-develop/routes/routes.go - API routes → Job synchronization: routes job requests
lead-services-develop/routes/routes.go - API routes → AI assistance: routes AI requests
lead-services-develop/routes/routes.go