adittyyaa/ticketing_sys_pv

Purpose and deployment shape

PV Advisory is a customer-support ticketing system split into a Next.js frontend and a Node.js API backend. Development entry points are the root scripts in package.json; service runtimes are frontend/package.json (port 3000) and backend/server.js (port 3001). Docker support exists in frontend/Dockerfile and backend/Dockerfile.

Frontend application shell and routing

The frontend uses Next.js App Router. Global composition begins in frontend/src/app/layout.tsx, with the primary landing surface at frontend/src/app/page.tsx. Auth, ticket inbox/detail/create, solutions, and administration are route-level boundaries:

• frontend/src/app/auth/page.tsx

• frontend/src/app/tickets/page.tsx

• frontend/src/app/tickets/[id]/page.tsx

• frontend/src/app/admin/overview/page.tsx

Authenticated UI is organized around reusable shell components in frontend/src/components/layout/AppShell.tsx, frontend/src/components/layout/Sidebar.tsx, and frontend/src/components/layout/TopBar.tsx.

Client state, session lifecycle, and API boundary

Frontend services isolate HTTP access to the backend: frontend/src/services/api.ts, frontend/src/services/authService.ts, and frontend/src/services/ticketService.ts. Auth initialization and inactivity logout are provider-level concerns in frontend/src/components/providers/AuthInitProvider.tsx and frontend/src/components/providers/InactivityLogoutProvider.tsx, with consumer hooks in frontend/src/hooks/useAuth.ts.

Control flow is UI route/component → feature service/API client → backend REST route. Theme and local UI persistence remain client-side through frontend/src/contexts/ThemeContext.tsx and frontend/src/hooks/useLocalStorage.ts.

Ticketing and knowledge-management UI

Tickets are the dominant workflow: browse/filter via frontend/src/components/features/tickets/TicketInboxView.tsx and frontend/src/components/features/tickets/TicketFilterDrawer.tsx; inspect ticket records through frontend/src/components/features/tickets/CommentsSection.tsx and frontend/src/components/features/tickets/AttachmentsSection.tsx. The separate solutions area is exposed at frontend/src/app/solutions/page.tsx and calls frontend/src/services/solutionService.ts. Feedback is a parallel user-facing workflow through frontend/src/services/feedbackService.ts and frontend/src/components/modals/FeedbackModal.tsx.

Backend HTTP pipeline

backend/server.js is the API process entry point. It composes route registration from backend/routes/index.js, which partitions the REST surface into auth, tickets, solutions, feedback, and administration:

• backend/routes/auth.js

• backend/routes/tickets.js

• backend/routes/admin.js

Cross-cutting request boundaries are middleware for authentication, validation, security/CORS, logging, and failure handling: backend/middleware/auth.js, backend/middleware/validation.js, and backend/middleware/errorHandler.js. Thus the expected flow is request → middleware → route/controller → service → model/database → response.

Backend domain and persistence layers

Controllers adapt HTTP operations into domain services, notably backend/controllers/ticketController.js, backend/controllers/authController.js, and backend/controllers/solutionController.js. Services centralize ticket, comment, authentication, user, feedback, and solution operations in backend/services/ticketService.js, backend/services/commentService.js, and backend/services/authService.js.

Persistence is PostgreSQL-backed per the project documentation. Connection/configuration boundaries are backend/config/database.js and backend/lib/database.js. Core relational/domain records include backend/models/Ticket.js, backend/models/User.js, backend/models/Comment.js, plus attachments, categories, tags, ticket types, custom statuses, feedback, and solutions.

Operations and infrastructure

The system expects PostgreSQL and optionally PgAdmin alongside the two application services. Database bootstrap and production/schema operations are represented by backend/scripts/setup-production-db.js, backend/scripts/verify-schema.js, and backend/utils/database-setup-postgresql.sql. Backend performance work includes SQL changes in backend/performance-fixes.sql, monitoring in backend/performance-monitor.js, and caching infrastructure in backend/utils/cache.js.