Skip to content

daily-documentation.md

Latest commit

 

History

History
2492 lines (2117 loc) · 99.6 KB

daily-documentation.md

File metadata and controls

2492 lines (2117 loc) · 99.6 KB
Raw

Job‑Portal (Daily‑wise Documentation)

Day 1 — Auth Service Base + Infrastructure

Goal: Auth service का बेस सेटअप, DB schema, Redis, Kafka producer.

Highlights

Key Components

  • app initialization: express.json() + routes mounting.
  • initDb() bootstraps schema on startup.
  • connectKafka() ensures topic exists before producing.

Day 2 — Auth Features + File Upload + Error Handling

Goal: Register/Login/Forgot/Reset password flows और file upload handling.

Highlights

Key Flows

  • Register (jobseeker): Multer file → Data URI → Upload service → DB insert → JWT.
  • Forgot Password: JWT (15m) → Redis store (forgot:<email>) → Kafka send-mail.
  • Reset Password: JWT verify + Redis token match → password update → Redis delete.

Day 3 — Utils Service (Mail Consumer + File Upload API)

Goal: Kafka mail consumer + Cloudinary upload API.

Highlights

Key Flow

  • Send Mail: Kafka message → Nodemailer SMTP → email sent.
  • Upload: Client sends buffer → Cloudinary upload → URL returned.

Day 4 — User Service Setup

Goal: User service ka base setup aur initial contents add karna.

Highlights

Notes

Day 5 — User Profile CRUD Features

Goal: User service me complete profile management features add karna.

Highlights

  • Dependencies Update: Axios aur its type definitions add kiye for HTTP communication.
    services/user/package.json
    • Added: axios@1.13.5 and @types/axios@0.9.36
  • Get User Profile by ID: Kisi bhi user ka profile fetch karne ka endpoint.
    services/user/src/controllers/user.ts
    • getUserProfile() function with SQL query including user_skills and skills join
    • Aggregates skills array using ARRAY_AGG
    • 404 error handling if user not found
  • Update User Profile: User apna basic info update kar sake.
    services/user/src/controllers/user.ts
    • updateUserProfile() updates name, phone_number, bio
    • Authenticated users only (via isAuth middleware)
  • Update Profile Picture: User apni profile pic upload/replace kar sake.
    services/user/src/controllers/user.ts
    • updateProfilePic() uses multer for file upload
    • Converts file to buffer using getBuffer()
    • Sends buffer to utils service via axios POST to /api/utils/upload
    • Old profile pic replace ho jati hai (via public_id)
    • Updates DB with new URL and public_id
  • New Routes: 3 new routes added.
    services/user/src/routes/user.ts
    • GET /:userId - Get any user's profile (authenticated)
    • PUT /update/profile - Update own profile info (authenticated)
    • PUT /update/pic - Update profile picture (authenticated + multer)

Key Flows

  • Get User Profile: Client sends userId → SQL query with joins → Returns user + skills array
  • Update Profile: Client sends JSON → Validate auth → Update DB → Return updated fields
  • Update Profile Pic: Client uploads file → Multer processes → Buffer conversion → Axios POST to utils service → Update DB with Cloudinary URL

Technical Details

  • Axios configuration includes type safety with TypeScript generics
  • Error handling via ErrorHandler for 400/401/404 scenarios
  • All profile operations require JWT authentication
  • Profile pic update integrates with existing utils/upload service

Day 6 — Resume Upload + Skills Management (User Service)

Goal: User resume update aur complete skill management features.

Highlights

  • Update Resume: User resume upload aur replace functionality complete.
    services/user/src/controllers/user.ts
    • updateResume() handles file upload via multer
    • Converts file to buffer aur sends to utils service
    • Old resume replace via resume_public_id
    • Returns updated user with new resume URL
  • Add Skill to User: Complete transaction-based skill add flow.
    services/user/src/controllers/user.ts
    • addSkillToUser() validates skill name
    • SQL transaction: INSERT skill (ON CONFLICT update) + INSERT user_skills (ON CONFLICT do nothing)
    • Returns 200 if skill already exists, 201-like response if added
    • Proper COMMIT/ROLLBACK transaction handling
  • Delete Skill from User: User skill removal capability.
    services/user/src/controllers/user.ts
    • deleteSkillFromUser() deletes from user_skills where skill name matches
    • Throws 404 if skill not found for user
  • Auth Middleware Fix: Minor import cleanup (removed unused e variable).
    services/user/src/middleware/auth.ts
  • New Routes: 3 new endpoints wired.
    services/user/src/routes/user.ts
    • PUT /update/resume - Upload/replace resume (authenticated + multer)
    • POST /skill/add - Add skill to user (authenticated, JSON body)
    • DELETE /skill/delete - Remove skill from user (authenticated, JSON body)

Key Flows

  • Update Resume: Client uploads → Multer processes → Axios POST to utils service → DB update
  • Add Skill: Skill name → Check user exists → Insert skill (or reuse) → Link to user_skills → Transaction commit
  • Delete Skill: Skill name → DELETE from user_skills → Validate deletion → Return success message

Technical Details

  • Transaction handling with BEGIN/COMMIT/ROLLBACK for data consistency
  • ON CONFLICT clauses prevent duplicate skills + user_skill links
  • deleteSkillFromUser() uses subquery to find skill_id by name
  • All operations require JWT authentication

Day 7 — Job Service Setup + DB Schema

Goal: Job service ka base setup aur database schema initialize karna.

Highlights

Key Flows

  • Service boot initializes DB schema before starting server.
  • Auth middleware validates JWT and attaches user context.

Day 8 — Job + Company APIs (Job Service)

Goal: Company and job management endpoints implement karna.

Highlights

  • Company management endpoints (create, delete, list, details).
    services/job/src/controllers/job.ts
    • createCompany() recruiter-only with logo upload via utils service
    • deleteCompany() recruiter-only delete (company ownership check)
    • getAllCompany() lists recruiter companies
    • getCompanyDetails() returns company with jobs via JSON aggregate
  • Job management endpoints (create, update, list, single).
    services/job/src/controllers/job.ts
    • createJob() recruiter-only, validates company ownership
    • updateJob() recruiter-only, ownership validation
    • getAllActiveJobs() public listing with title/location filters
    • getSingleJob() fetch by job id
  • Job routes wired under /api/job.
    services/job/src/routes/job.ts

Key Flows

  • Create Company: Logo upload → utils upload API → company insert
  • Create Job: Recruiter auth → company ownership check → job insert
  • List Jobs: Public search via query filters + active jobs only

Day 9 — Job Application Flow (User Service)

Goal: Jobseeker side se job apply karna aur apni applications dekhna.

Highlights

  • User controller me job application features add kiye.
    services/user/src/controllers/user.ts
    • applyForJob() added with jobseeker-only guard
    • Resume-required validation before applying
    • Duplicate application handling (23505 unique violation -> 409)
    • Subscription-based priority flag (subscribed) set at apply time
    • getAllaplications() added to list current user's applications with job details
  • New user routes add kiye.
    services/user/src/routes/user.ts
    • POST /apply/job
    • GET /application/all

Key Flows

  • Apply Job: JWT auth -> role check (jobseeker) -> resume presence check -> job active check -> application insert.
  • List My Applications: Authenticated user -> join applications + jobs -> all own applications return.

Day 10 — Recruiter Application Management + Kafka Mail (Job Service)

Goal: Recruiter ko job applications manage karne aur status update par email trigger karne ka flow.

Highlights

Key Flows

  • Recruiter View Applications: Recruiter auth -> job ownership verify -> applications sorted by subscribed DESC, applied_at ASC.
  • Update Application Status: Recruiter auth -> ownership verify -> status update -> Kafka event publish -> utils service sends email.

Day 11 — AI Career Guidance + Resume ATS Analysis (Utils Service)

Goal: Utils service me Gemini AI based career and resume analysis endpoints add karna.

Highlights

  • Utils service dependencies me Gemini SDK add kiya.
    services/utils/package.json
    • Added: @google/genai
  • Utils env example me Gemini API key variable add hua.
    services/utils/.env.example
    • Added: API_KEY_GEMINI
  • Utils routes me AI endpoints implement kiye.
    services/utils/src/routes.ts
    • POST /career for skill-based career roadmap response in JSON
    • POST /resume-analyser for ATS score + suggestions from resume PDF
    • Response sanitization/parsing logic to convert AI output into strict JSON

Key Flows

  • Career Guidance: Skills input -> Gemini prompt -> structured JSON parse -> career path response.
  • Resume Analysis: PDF base64 input -> Gemini multimodal request -> ATS JSON response (score + improvements).

Day 12 — Frontend Project Initialization (Next.js + shadcn/ui)

Goal: Job portal ka frontend project scaffold karna Next.js ke saath, theming aur UI component library setup karna.

Highlights

Key Flows

  • Theme: ThemeProvider (next-themes) → ModeToggle dropdown → class-based dark mode via "use client" + useTheme().
  • Styling pipeline: Tailwind CSS v4 → @tailwindcss/postcss → CSS variables (oklch) → shadcn token system → component classes via cn().

Day 13 — Responsive NavBar Component + DropdownMenu

Goal: Full site navigation bar banana jo desktop + mobile dono pe responsive ho, auth-aware ho, aur dark mode support kare.

Highlights

  • DropdownMenu shadcn component added via CLI (npx shadcn@latest add dropdown-menu).
    frontend/src/components/ui/dropdown-menu.tsx
    • Components exported: DropdownMenu, DropdownMenuTrigger, DropdownMenuContent, DropdownMenuItem, DropdownMenuSeparator, DropdownMenuLabel, DropdownMenuSub, and more.
  • NavBar component built — sticky, blurred, bordered top navigation.
    frontend/src/components/navbar.tsx
    • Logo: "HireHeaven" with gradient blue/red styling.
    • Desktop nav links: Home (/), Jobs (/jobs), About (/about) using Button ghost variant.
    • Auth-aware right side:
      • Authenticated: Avatar with Popover showing user name, email, "My Profile" link, and "Logout" button.
      • Unauthenticated: "Sign In" button linking to /login.
    • Mobile menu: animated slide-in panel (max-h transition), hamburger icon (Menu) toggles to close (X). All nav links, profile, and logout replicated.
    • ModeToggle present in both desktop and mobile views.
    • isAuth and logoutHandler placeholders set for future Redux/context integration.
  • Home page (page.tsx) scaffolded with a test Button.
    frontend/src/app/page.tsx

Key Flows

  • Mobile toggle: toggleMenu() → isOpen state → max-h-96 / max-h-0 transition for smooth open/close.
  • Auth UI: isAuth boolean → conditional render of Avatar+Popover (logged in) or Sign In button (logged out).
  • Theme toggle: ModeToggle (DropdownMenu) → setTheme("light"|"dark"|"system") → ThemeProvider updates class on <html>.

Day 14 — Services CORS + Route Access + Auth Flow Fixes

Goal: Services layer me cross-origin access aur route behavior ko frontend integration ke liye stabilize karna.

Highlights

Key Outcomes

  • Frontend se Auth/Job/User services par direct requests ke liye CORS blockers remove hue.
  • Company details endpoint unauthenticated users ke liye accessible hua (public job discovery flow).
  • Auth-to-utils upload call path consistency improve hui (/api/utils/upload).

Day 15 — Frontend Foundation Sync

Goal: Frontend base shell, dependencies, aur global styling ko stable state me lana.

Highlights

Key Flows

  • Install/run consistency: npm install -> npm run dev -> no dependency drift.

Day 16 — Home and Navigation Stabilization

Goal: Landing page aur navigation ko responsive aur consistent banana.

Highlights

Key Flows

  • Navbar state transitions verify: desktop menu, mobile toggle, auth-aware actions.

Day 17 — Auth Screens Completion

Goal: Login/register/forgot/reset user journey ko complete karna.

Highlights

Key Flows

  • User auth flow: register/login -> forgot password -> reset by token.

Day 18 — Shared Types and Context Layer

Goal: Frontend me shared data contracts aur global context ko stabilize karna.

Highlights

Key Flows

  • Typed state flow: context provider -> consumer components -> predictable UI state.

Day 19 — Jobs Listing Experience

Goal: Jobs listing page ko production-ready discovery UX dena.

Highlights

Key Flows

  • Job browse flow: list render -> card view -> details navigation.

Day 20 — Job Details and Loading States

Goal: Single job page aur async states ko polish karna.

Highlights

Key Flows

  • Job details flow: fetch -> loading -> success/error state handling.

Day 21 — Company Details Page

Goal: Company profile route ko public viewing ke liye complete karna.

Highlights

Key Flows

  • Company discovery: company page open -> company info + jobs mapping display.

Day 22 — Account Dashboard Base

Goal: Account routes ka base profile shell complete karna.

Highlights

Key Flows

  • Account route flow: /account -> /account/[id] with structured sections.

Day 23 — Account Subcomponents Completion

Goal: Account screen ke modular sections complete karna.

Highlights

Key Flows

  • Account modules flow: profile info -> skills -> company -> applied jobs.

Day 24 — Subscription and Payment Success Flow

Goal: Subscription-to-payment success user journey complete karna.

Highlights

Key Flows

  • Conversion flow: subscribe action -> payment callback -> success state rendering.

Day 25 — AI Utility Components Integration

Goal: Career guide aur resume analyser components ko app flow me align karna.

Highlights

Key Flows

  • AI utility flow: input capture -> processing -> structured output display.

Day 26 — Script Loader and External Integration Safety

Goal: External script handling ko safe lifecycle behavior ke saath stabilize karna.

Highlights

Key Flows

  • External SDK flow: mount -> load -> ready -> cleanup.

Day 27 — UI Primitives Consistency Pass

Goal: Reusable UI primitives me design and behavior consistency maintain karna.

Highlights

Key Flows

  • Component reuse flow: common props -> shared styles -> predictable interaction patterns.

Day 28 — About Page and Asset Polish

Goal: Branding assets aur static pages ko final polish dena.

Highlights

Key Flows

  • Static render flow: route open -> optimized image assets -> stable layout.

Day 29 — Cross-Route QA and Regression

Goal: Full frontend routes ka integration QA pass complete karna.

Highlights

  • Route-to-route manual regression run kiya gaya (auth -> jobs -> account -> subscribe).
  • API response mapping verify ki gayi with active backend endpoints.

Key Flows

  • End-to-end smoke flow: authentication -> browsing -> profile actions -> payment confirmation.

Day 30 — Release Readiness and Documentation Freeze

Goal: Final bug-fix closure aur release documentation complete karna.

Highlights

  • QA backlog se critical UI/flow issues close kiye gaye.
  • Frontend release summary and documentation freeze complete hua.

Key Flows

  • Release handover flow: final validation -> docs sync -> deployment-ready state.

Day 31 — Frontend Route Integration (Auth + Core Pages)

Goal: Core user-facing routes ko fully integrated state me document aur align karna.

Highlights

Key Flows

  • Visitor flow: Home -> About -> Auth pages -> back to protected features.

Day 32 — Jobs + Company Module Consolidation

Goal: Job discovery aur company information flows ko stable user journey me complete karna.

Highlights

Key Flows

  • Discovery flow: Job list -> Job details -> Company details.

Day 33 — Account + Subscription Journey Completion

Goal: User account dashboard aur subscription/payment flow ko end-to-end complete karna.

Highlights

Key Flows

  • User flow: Profile dashboard -> plan subscribe -> payment success callback.

Day 34 — Shared UI System + State Layer Alignment

Goal: Reusable UI primitives, shared types, aur context ko maintainable structure me align karna.

Highlights

Key Flows

  • Component reuse flow: shared props + shared variants -> predictable UI rendering.

Day 35 — AI Utilities + Script Integration Finalization

Goal: AI utility features aur external script flows ko finalize karna.

Highlights

Key Flows

  • AI interaction flow: input -> process -> structured output render.

Day 36 — Frontend Performance Optimization Pass

Goal: Frontend performance ko optimize karke faster load/render experience dena.

Highlights

Key Flows

  • Image Rendering Flow: Optimized image component -> lazy fetch -> stable layout rendering.
  • Listing Performance Flow: Data list -> memoized filtering -> paginated slice -> reduced DOM render cost.
  • Search Performance Flow: User typing -> debounce delay -> controlled API calls -> smooth interaction.

Optimization Coverage

  • Image optimization + lazy loading for media-heavy UI.
  • On-demand component loading for modal/secondary interactions.
  • Pagination for large datasets to reduce initial render load.
  • Debounced search/filter calls to avoid API thrashing.

Day 37 — Payment Service Integration + Auth/Frontend Hardening

Goal: Subscription payment flow ko backend service level par introduce karna aur related auth/frontend reliability improve karna.

Highlights

Key Flows

  • Checkout Flow: Authenticated user -> subscription validity check -> Razorpay order creation.
  • Verification Flow: Razorpay callback payload -> HMAC signature verification -> user subscription expiry update.
  • Frontend Payment Init Flow: Env Razorpay key resolve -> script load success/failure handling -> checkout open.

Day 38 — Dockerization + Compose Orchestration

Goal: Project ko containerized local stack me run/deploy karne ke liye complete Docker setup add karna.

Highlights

Key Flows

  • Compose Boot Flow: docker compose up --build -> infra healthcheck pass -> service containers start.
  • Container Runtime Flow: Service image build -> compiled output/run command -> exposed port mapping.
  • Env-driven Deployment Flow: .env.docker values -> compose environment injection -> consistent local stack behavior.

Day 39 — Kafka → Bull Queue Refactoring

Goal: Async email messaging ko Kafka se Bull Queue (Redis-based) mein migrate karke infrastructure simplify karna.

Highlights

  • Auth Service ne Kafka ko Bull Queue mein replace kiya for email job queuing.
    services/auth/src/app.ts
    services/auth/src/producer.ts
    • connectKafka() naa naam hai par Bull Queue init karta hai
    • publishToTopic() emails ko queue mein add karta hai with 3 retry attempts + exponential backoff
    • package.json mein bull v4.11.5 aur redis v5.10.0 add kiye gaye
  • Job Service ne same pattern follow kiya with Bull Queue for email publishing.
    services/job/src/app.ts
    services/job/src/producer.ts
    • Email queuing logic Bull-based hai now
    • Retry + timeout error suppression implemented
  • Utils Service ne Bull Queue consumer setup kiya with Nodemailer integration.
    services/utils/src/consumer.ts
    services/utils/src/index.ts
    • startSendMailConsumer() Bull queue process job listeners setup karta hai
    • Queue process 5 concurrent jobs handle karta hai
    • Nodemailer SMTP via Gmail configured
    • Job failures par auto-retry with exponential backoff (2s delay)
    • Redis TLS support for Upstash serverless setup
  • Docker files aur Kafka infrastructure removed (local dev simplification ke liye).
    • Deleted: docker-compose.yml, Dockerfile (all services), .dockerignore (all services), .env.docker.example
  • All .env.example files updated to remove Kafka + Docker references.
    services/auth/.env.example, services/user/.env.example, etc.

Key Flows

  • Email Queue Flow (Auth/Job): Service event -> publishToTopic() call -> Bull queue job add -> return immediately (non-blocking).
  • Email Processing Flow (Utils): Bull job listener active -> emailQueue.process() handler -> Nodemailer SMTP send -> on success/failure log.
  • Retry Flow: Job fails -> exponential backoff (2s delay) -> 3 max attempts -> if all fail, error logged + job discarded.
  • Env-driven Connectivity: Redis URL from REDIS_URL env -> TLS rejectUnauthorized false -> Upstash compatible.

Day 40 — Queue Naming Cleanup + Auth Logging Hardening

Goal: Bull Queue migration ke baad naming consistency improve karna, auth error logs harden karna, aur frontend lint-safe subscription check clarify karna.

Highlights

Key Flows

  • Queue Bootstrap Flow: service start -> initEmailQueue() call -> queue client initialize -> request handlers non-blocking publish continue.
  • Failure Observability Flow: auth failure catch -> scoped console.error message -> consistent debugging context across services.
  • Time-based Subscription Flow: subscription timestamp compare with current time (Date.now()) -> active/inactive badge resolution.

Day 41 — Reference-Only Change Mapping

Goal: Latest refactor changes ko quick traceability ke liye sirf direct file references ke through map karna.

Highlights

Key Flows

Day 42 — Resend Email Pipeline + Template Integration

Goal: Email delivery stack ko Gmail SMTP se Resend API par migrate karke auth/payment events ke liye richer transactional templates integrate karna.

Highlights

Key Flows

  • Auth Welcome/Login Flow: register/login event -> queue publish -> utils consumer -> Resend API dispatch.
  • Subscription Invoice Flow: payment verify success -> invoice template payload -> send-mail queue -> Resend delivery.
  • Provider Migration Flow: SMTP config dependency removal -> API key based Resend client init -> transactional send operation.

Day 43 — Bull Queue Removal + Direct Resend API Migration

Goal: Email queue delays causing spam issues ko eliminate karne ke liye Bull Queue architecture ko completely remove karke direct Resend API calls integrate karna.

Problem Identified

  • Bull Queue based system emails mein 30+ second delay add kar raha tha
  • Queue processing batch-wise hota tha jisse spam filters ko suspicious pattern dikhta tha
  • Peak hours par queue backlog build hota tha aur delivery fail hota tha
  • Original Kafka setup ne direct send karta tha, Bull Queue ne bottleneck create kiya

Highlights

  • Auth Service ab direct Resend API calls use karta hai for all email events.
    services/auth/src/controllers/auth.ts
    • RegisterUser endpoint ab instant welcome email send karta hai (no queue)
    • LoginUser endpoint ab instant login alert email send karta hai
    • ForgotPassword endpoint ab instant reset link email send karta hai
    • All endpoints use new Resend(process.env.RESEND_API_KEY) + resend.emails.send() pattern
    • Producer.ts completely remove kar diya gaya
    • Package.json se bull + redis dependencies remove, resend package add kiya
  • Payment Service ab direct Resend API calls use karta hai for subscription invoices.
    services/payment/src/controllers/payment.ts
    • PaymentVerification endpoint ab instant subscription invoice email send karta hai
    • resend.emails.send() synchronous call with subscription template
    • Producer.ts completely remove kar diya gaya
    • Package.json se bull dependencies remove, resend package add kiya
  • App initialization se Queue bootstrap code completely removed.
    services/auth/src/app.ts
    services/payment/src/index.ts
    • initEmailQueue() import aur call completely remove kar diya
    • No queue client initialization overhead on startup
    • Faster app startup time
  • Utils Service ke unused queue infrastructure clean up.
    services/utils/src/consumer.ts — DELETED
    • Bull Queue consumer completely remove kar diya, ab koi email processing nahi
    • Utils service ab sirf AI endpoints + file uploads handle karta hai
  • Redis ab sirf password reset tokens store karta hai (queue nahi).
    • Connection overhead minimal
    • Upstash Redis cost further optimize ho sakta hai

Email Flow (NEW)

User Register/Login/Forgot Password Event
  -> Auth Controller
  -> resend.emails.send({ to, from, subject, html })
  -> Resend API instant delivery
  -> Email in inbox within seconds (no queue delay)

Benefits Achieved

  • ✅ Zero queue delay: 30+ seconds → 0 seconds
  • ✅ Instant delivery: Email sends with request completion
  • ✅ Higher deliverability: Resend provider integration with verified sender domain
  • ✅ Simpler architecture: No consumer/producer pattern overhead
  • ✅ Better spam scores: Instant single emails vs batch queue patterns
  • ✅ Faster app startup: No queue client initialization
  • ✅ Reduced complexity: Less moving parts to debug

Code Changes Summary

  • Auth Service: 4 files modified (1 deleted, including producer.ts)
  • Payment Service: 4 files modified (1 deleted, including producer.ts)
  • Utils Service: 1 file deleted (consumer.ts)
  • Total lines removed: ~400 lines of queue boilerplate
  • Total files deleted: 3 (producer.ts × 2, consumer.ts)

Key Flows

  • Direct Email Flow: Register/Login/Forgot → resend.emails.send() → Response 200
  • Subscription Email Flow: PaymentVerify success → resend.emails.send() → Invoice delivered
  • No Queue Flow: Eliminated completely, replaced with synchronous Resend API

Deployment Notes

  • All 5 services continue running (Utils service no longer has queue consumer)
  • Railway auto-redeploy picks up new code
  • RESEND_API_KEY must be set in environment variables
  • Sender email verification: onboarding@resend.dev (verified in Resend)

Day 44 — Admin Panel + Multi-Service Admin APIs

Goal: Platform-level moderation aur monitoring ke liye full admin panel rollout karna with backend admin routes across User, Job, aur Payment services.

Highlights

Key Flows

  • Admin Auth Flow: /admin/login password input -> test call (/api/admin/users/stats) with x-admin-key -> valid key store -> protected panel access.
  • Cross-Service Dashboard Flow: frontend dashboard -> parallel fetch to User/Job/Payment admin stats APIs -> unified analytics cards/charts.
  • Admin Operations Flow: panel action (delete/update/filter) -> corresponding service admin endpoint -> DB update -> UI refresh.

API Endpoints Table

Auth Service (Base: /api/auth)

Method Endpoint Description Body/Params Notes
POST /register User register JSON + file (jobseeker) role = jobseeker requires resume file field file
POST /login User login JSON Returns JWT + user data
POST /forgot Send reset link JSON Sends reset email directly via Resend
POST /reset/:token Reset password JSON + URL param Token valid 15 min

Source: services/auth/src/routes/auth.ts

Utils Service (Base: /api/utils)

Method Endpoint Description Body Notes
POST /upload Upload/replace file JSON If public_id present, old file is deleted
POST /career AI career suggestion JSON Body: { skills: "..." }, returns structured career roadmap
POST /resume-analyser AI ATS resume analysis JSON Body: { pdfBase64: "..." }, returns score + suggestions

Source: services/utils/src/routes.ts

User Service (Base: /api/user)

Method Endpoint Description Body/Params Notes
GET /me Get current user profile Header Requires Authorization: Bearer <token>
GET /:userId Get user profile by ID URL param + Header Requires auth, returns user with skills
PUT /update/profile Update user profile JSON + Header Updates name, phoneNumber, bio
PUT /update/pic Update profile picture FormData + Header Requires file upload via multer
PUT /update/resume Update resume FormData + Header Requires file upload via multer
POST /skill/add Add skill to user JSON + Header Body: { skillName: "..." }
DELETE /skill/delete Remove skill from user JSON + Header Body: { skillName: "..." }
POST /apply/job Apply for a job JSON + Header Jobseeker-only, requires uploaded resume
GET /application/all Get my applications Header Returns applicant's applied jobs list

Source: services/user/src/routes/user.ts

Job Service (Base: /api/job)

Method Endpoint Description Body/Params Notes
POST /company/new Create company FormData + Header Recruiter-only, logo file required
DELETE /company/:companyId Delete company URL param + Header Recruiter-only, ownership required
GET /company/all List recruiter companies Header Recruiter-only
GET /company/:id Company details + jobs URL param Includes jobs array
POST /new Create job JSON + Header Recruiter-only, company ownership required
PUT /:jobId Update job JSON + Header Recruiter-only, ownership required
GET /all List active jobs Query params Optional title, location filters
GET /:jobId Get single job URL param Public
GET /application/:jobId Get applications for a job URL param + Header Recruiter-only, job ownership required
PUT /application/update/:id Update application status URL param + JSON + Header Recruiter-only, triggers status email

Source: services/job/src/routes/job.ts

Payment Service (Base: /api/payment)

Method Endpoint Description Body/Params Notes
POST /checkout Create Razorpay order Header Auth required, blocks duplicate active subscription
POST /verify Verify Razorpay payment and activate subscription JSON + Header Auth required, validates razorpay_signature

Source: services/payment/src/routes/payment.ts

User Admin Routes (Base: /api/admin on User Service)

Method Endpoint Description Body/Params Notes
GET /users/all List users with pagination/search/filter Query params Requires x-admin-key
GET /users/stats User dashboard stats Header Returns totals by role + subscribed count
GET /users/role/:role Users by role URL param role: recruiter/jobseeker
GET /users/:userId Get single user profile URL param Admin-level lookup
PUT /users/update/:userId Update user profile fields JSON + URL param Admin edit flow
DELETE /users/delete/:userId Delete user and linked skills URL param Cascading clean-up handled

Source: services/user/src/routes/admin.ts

Job Admin Routes (Base: /api/admin on Job Service)

Method Endpoint Description Body/Params Notes
GET /jobs/all List all jobs with pagination/search Query params Includes company join data
GET /jobs/stats Job/application/company summary Header Dashboard aggregation
DELETE /jobs/delete/:jobId Delete job + linked applications URL param Admin destructive action
GET /applications/all List applications with status filter Query params Supports status-based filtering
PUT /applications/update/:applicationId Update application status JSON + URL param Valid statuses enforced
GET /companies/all List companies with job counts Header Grouped company overview
DELETE /companies/delete/:companyId Delete company + dependent jobs/apps URL param Full cleanup flow

Source: services/job/src/routes/admin.ts

Payment Admin Routes (Base: /api/admin on Payment Service)

Method Endpoint Description Body/Params Notes
GET /payments/stats Subscription metrics + revenue estimate Header Requires x-admin-key
GET /subscriptions/all Paginated subscription listing Query params Includes status + expiry

Source: services/payment/src/routes/admin.ts

Setup/Run Steps

Frontend

  1. Navigate to frontend/ directory.
  2. Install dependencies: npm install.
  3. Start dev server: npm run dev (runs on http://localhost:3000).

Scripts: npm run dev, npm run build, npm run start, npm run lint
Source: frontend/package.json

Required: Backend services running and accessible for API calls.

Auth Service

  1. Create .env using services/auth/.env.example.
  2. Install dependencies.
  3. Build and start.

Scripts: npm run build, npm run start, npm run dev
Source: services/auth/package.json

Utils Service

  1. Create .env using services/utils/.env.example.
  2. Install dependencies.
  3. Build and start.

Scripts: npm run build, npm run start, npm run dev
Source: services/utils/package.json

Required Services

  • Redis, Postgres/Neon, Cloudinary, Resend API

User Service

  1. Create .env (see Environment Variables Details).
  2. Install dependencies.
  3. Build and start.

Scripts: npm run build, npm run start, npm run dev
Source: services/user/package.json

Job Service

  1. Create .env using services/job/.env.example.
  2. Install dependencies.
  3. Build and start.

Scripts: npm run build, npm run start, npm run dev
Source: services/job/package.json

Payment Service

  1. Create .env using services/payment/.env.example.
  2. Install dependencies.
  3. Build and start.

Scripts: npm run build, npm run start, npm run dev
Source: services/payment/package.json

Architecture Diagram (Text)

Browser (Next.js Frontend)
  |-- React 19 + TypeScript
  |-- Next.js 16 App Router
  |-- shadcn/ui (Tailwind CSS v4 + Radix UI)
  |-- next-themes (dark/light/system)
  |
  | HTTP /api/auth/*
  v
Auth Service (Express)
  |-- PostgreSQL (Neon)  [users, skills, user_skills]
  |-- Redis             [forgot:<email> token]
  |-- Kafka Producer    [send-mail]
  |
  | HTTP /api/utils/upload
  v
Utils Service (Express)
  |-- Cloudinary         [file storage]
  |-- Kafka Consumer     [send-mail]
  |-- SMTP (Nodemailer)  [email dispatch]
  |-- Gemini API         [career guidance + ATS analysis]

Browser (Next.js Frontend)
  |
  | HTTP /api/user/*
  v
User Service (Express)
  |-- PostgreSQL (Neon)  [users, skills, user_skills]
  |
  | HTTP /api/utils/upload
  v
Utils Service (Express)
  |-- Cloudinary         [profile pic storage]
  |-- Gemini API         [career guidance + ATS analysis]

Browser (Next.js Frontend)
  |
  | HTTP /api/job/*
  v
Job Service (Express)
  |-- PostgreSQL (Neon)  [companies, jobs, applications]
  |-- Kafka Producer     [send-mail on application status update]
  |
  | HTTP /api/utils/upload
  v
Utils Service (Express)
  |-- Cloudinary         [company logos]
  |-- Kafka Consumer     [send-mail]
  |-- SMTP (Nodemailer)  [status update email]
  |-- Gemini API         [career guidance + ATS analysis]

Environment Variables Details

Auth Service

Source: services/auth/.env.example

Variable Purpose
PORT Service port
DB_URL Neon/Postgres connection string
UPLOAD_SERVICE Utils service base URL (for resume upload)
JWT_SEC JWT secret key
KAFKA_BROKER Kafka broker address
FRONTEND_URL Frontend base URL (reset link)
REDIS_URL Redis connection URL

Utils Service

Source: services/utils/.env.example

Variable Purpose
PORT Service port
CLOUD_NAME Cloudinary cloud name
API_KEY Cloudinary API key
API_SECRET Cloudinary API secret
KAFKA_BROKER Kafka broker address (code uses KAFKA_BROKER)
SMTP_USER SMTP user email
SMTP_PASS SMTP password
API_KEY_GEMINI Gemini API key for AI endpoints

User Service

Source: services/user/.env.example

Variable Purpose
PORT Service port
DB_URL Neon/Postgres connection string
JWT_SEC JWT secret key
UPLOAD_SERVICE Utils service base URL (for profile pic upload)

Job Service

Source: services/job/.env.example

Variable Purpose
PORT Service port
DB_URL Neon/Postgres connection string
UPLOAD_SERVICE Utils service base URL (for company logo upload)
JWT_SEC JWT secret key
KAFKA_BROKER Kafka broker address

Payment Service

Source: services/payment/.env.example

Variable Purpose
PORT Payment service port
Razorpay_Key Razorpay key ID
Razorpay_Secret Razorpay key secret
DB_URL Neon/Postgres connection string
JWT_SEC JWT secret key

Sample Requests/Responses

Register (Recruiter)

Request

POST /api/auth/register
Content-Type: application/json

{
  "name": "Aman",
  "email": "aman@example.com",
  "password": "Pass@123",
  "phoneNumber": "9999999999",
  "role": "recruiter"
}

Response

{
  "message": "User registered successfully",
  "registeredUser": {
    "user_id": 1,
    "name": "Aman",
    "email": "aman@example.com",
    "phone_number": "9999999999",
    "role": "recruiter",
    "created_at": "2026-02-03T10:00:00.000Z"
  },
  "token": "<jwt>"
}

Register (Jobseeker)

Request

POST /api/auth/register
Content-Type: multipart/form-data

Fields:
  name=Aman
  email=aman@example.com
  password=Pass@123
  phoneNumber=9999999999
  role=jobseeker
  bio=Frontend developer
  file=<resume.pdf>

Login

Request

POST /api/auth/login
Content-Type: application/json

{
  "email": "aman@example.com",
  "password": "Pass@123"
}

Response

{
  "message": "User logged in successfully",
  "userObject": {
    "user_id": 1,
    "name": "Aman",
    "email": "aman@example.com",
    "phone_number": "9999999999",
    "role": "recruiter",
    "skills": []
  },
  "token": "<jwt>"
}

Forgot Password

Request

POST /api/auth/forgot
Content-Type: application/json

{
  "email": "aman@example.com"
}

Response

{
  "message": "If a user with that email exists, a password reset link has been sent"
}

Reset Password

Request

POST /api/auth/reset/:token
Content-Type: application/json

{
  "password": "NewPass@123"
}

Response

{
  "message": "Password has been reset successfully"
}

Upload (Utils Service)

Request

POST /api/utils/upload
Content-Type: application/json

{
  "buffer": "data:application/pdf;base64,JVBERi0xLjQK...",
  "public_id": "optional-existing-id"
}

Response

{
  "url": "https://res.cloudinary.com/.../file.pdf",
  "public_id": "abc123"
}

Career Guidance (Utils Service)

Request

POST /api/utils/career
Content-Type: application/json

{
  "skills": "React, Node.js, TypeScript, PostgreSQL"
}

Response

{
  "summary": "You are well-suited for modern full-stack product development roles.",
  "jobOptions": [
    {
      "title": "Full Stack Developer",
      "responsibilities": "Build and maintain frontend and backend features.",
      "why": "Your current stack aligns with production full-stack requirements."
    }
  ],
  "skillsToLearn": [
    {
      "category": "DevOps & Cloud",
      "skills": [
        {
          "title": "Docker",
          "why": "Helps with consistent deployment across environments.",
          "how": "Containerize a Node + Postgres project and deploy it."
        }
      ]
    }
  ],
  "learningApproach": {
    "title": "How to Approach Learning",
    "points": ["Build projects", "Follow roadmap", "Practice interviews"]
  }
}

Resume Analyser (Utils Service)

Request

POST /api/utils/resume-analyser
Content-Type: application/json

{
  "pdfBase64": "data:application/pdf;base64,JVBERi0xLjQK..."
}

Response

{
  "atsScore": 82,
  "scoreBreakdown": {
    "formatting": { "score": 85, "feedback": "Formatting is mostly ATS-friendly." },
    "keywords": { "score": 78, "feedback": "Add more role-specific keywords." },
    "structure": { "score": 84, "feedback": "Sections are well organized." },
    "readability": { "score": 81, "feedback": "Use more measurable outcomes." }
  },
  "suggestions": [
    {
      "category": "Keywords",
      "issue": "Missing exact job keywords",
      "recommendation": "Mirror target JD keywords in skills and experience",
      "priority": "high"
    }
  ],
  "strengths": ["Clear section structure", "Relevant project experience"],
  "summary": "Resume is solid and can improve further with stronger keyword matching."
}

My Profile (User Service)

Request

GET /api/user/me
Authorization: Bearer <jwt>

Response

{
  "user_id": 1,
  "name": "Aman",
  "email": "aman@example.com",
  "phone_number": "9999999999",
  "role": "recruiter",
  "bio": null,
  "resume": null,
  "profile_pic": null,
  "skills": []
}

Get User Profile by ID (User Service)

Request

GET /api/user/:userId
Authorization: Bearer <jwt>

Response

{
  "user_id": 2,
  "name": "Rahul",
  "email": "rahul@example.com",
  "phone_number": "8888888888",
  "role": "jobseeker",
  "bio": "Full stack developer",
  "resume": "https://res.cloudinary.com/.../resume.pdf",
  "resume_public_id": "resume_abc123",
  "profile_pic": "https://res.cloudinary.com/.../pic.jpg",
  "profile_pic_public_id": "pic_xyz789",
  "subscription": null,
  "skills": ["JavaScript", "React", "Node.js"]
}

Update User Profile (User Service)

Request

PUT /api/user/update/profile
Authorization: Bearer <jwt>
Content-Type: application/json

{
  "name": "Aman Kumar",
  "phoneNumber": "9999999990",
  "bio": "Senior recruiter with 5 years experience"
}

Response

{
  "message": "Profile updated successfully",
  "updatedUser": {
    "user_id": 1,
    "name": "Aman Kumar",
    "phone_number": "9999999990",
    "bio": "Senior recruiter with 5 years experience"
  }
}

Update Profile Picture (User Service)

Request

PUT /api/user/update/pic
Authorization: Bearer <jwt>
Content-Type: multipart/form-data

Fields:
  file=<profile-pic.jpg>

Response

{
  "message": "Profile picture updated successfully",
  "updatedUser": {
    "user_id": 1,
    "name": "Aman Kumar",
    "profile_pic": "https://res.cloudinary.com/.../new-pic.jpg"
  }
}

Update Resume (User Service)

Request

PUT /api/user/update/resume
Authorization: Bearer <jwt>
Content-Type: multipart/form-data

Fields:
  file=<resume.pdf>

Response

{
  "message": "Resume updated successfully",
  "updatedUser": {
    "user_id": 2,
    "name": "Rahul",
    "resume": "https://res.cloudinary.com/.../new-resume.pdf"
  }
}

Add Skill (User Service)

Request

POST /api/user/skill/add
Authorization: Bearer <jwt>
Content-Type: application/json

{
  "skillName": "Python"
}

Response (New Skill)

{
  "message": "Skill Python added to user successfully"
}

Response (Skill Already Exists)

{
  "message": "User already has this skill"
}

Delete Skill (User Service)

Request

DELETE /api/user/skill/delete
Authorization: Bearer <jwt>
Content-Type: application/json

{
  "skillName": "Python"
}

Response

{
  "message": "Skill Python deleted successfully"
}

Create Company (Job Service)

Request

POST /api/job/company/new
Authorization: Bearer <jwt>
Content-Type: multipart/form-data

Fields:
  name=Acme Corp
  description=Hiring platform for engineers
  website=https://acme.example
  file=<logo.png>

Response

{
  "message": "Company created successfully",
  "company": {
    "company_id": 1,
    "name": "Acme Corp",
    "logo": "https://res.cloudinary.com/.../logo.png",
    "logo_public_id": "company_logo_123"
  }
}

Create Job (Job Service)

Request

POST /api/job/new
Authorization: Bearer <jwt>
Content-Type: application/json

{
  "title": "Frontend Engineer",
  "description": "Build user-facing features",
  "salary": 120000,
  "location": "Bengaluru",
  "job_type": "Full-time",
  "openings": 2,
  "role": "Frontend",
  "work_location": "Hybrid",
  "company_id": 1
}

Response

{
  "message": "Job created successfully",
  "job": {
    "job_id": 10,
    "title": "Frontend Engineer",
    "company_id": 1
  }
}

Get Company Details (Job Service)

Request

GET /api/job/company/1

Response

{
  "company_id": 1,
  "name": "Acme Corp",
  "website": "https://acme.example",
  "jobs": [
    {
      "job_id": 10,
      "title": "Frontend Engineer"
    }
  ]
}

List Recruiter Companies (Job Service)

Request

GET /api/job/company/all
Authorization: Bearer <jwt>

Response

[
  {
    "company_id": 1,
    "name": "Acme Corp",
    "website": "https://acme.example"
  }
]

List Active Jobs (Job Service)

Request

GET /api/job/all?title=frontend&location=bengaluru

Response

[
  {
    "job_id": 10,
    "title": "Frontend Engineer",
    "company_name": "Acme Corp",
    "location": "Bengaluru"
  }
]

Get Single Job (Job Service)

Request

GET /api/job/10

Response

{
  "job_id": 10,
  "title": "Frontend Engineer",
  "company_id": 1
}

Update Job (Job Service)

Request

PUT /api/job/10
Authorization: Bearer <jwt>
Content-Type: application/json

{
  "title": "Frontend Engineer II",
  "description": "Build user-facing features",
  "salary": 140000,
  "location": "Bengaluru",
  "job_type": "Full-time",
  "openings": 1,
  "role": "Frontend",
  "work_location": "Hybrid",
  "company_id": 1,
  "is_active": true
}

Response

{
  "message": "Job updated successfully",
  "job": {
    "job_id": 10,
    "title": "Frontend Engineer II"
  }
}

Delete Company (Job Service)

Request

DELETE /api/job/company/1
Authorization: Bearer <jwt>

Response

{
  "message": "Company and all associated data deleted successfully"
}

Apply for Job (User Service)

Request

POST /api/user/apply/job
Authorization: Bearer <jwt>
Content-Type: application/json

{
  "job_id": 10
}

Response

{
  "message": "Application submitted successfully",
  "application": {
    "application_id": 21,
    "job_id": 10,
    "applicant_id": 2,
    "status": "Submitted"
  }
}

Get My Applications (User Service)

Request

GET /api/user/application/all
Authorization: Bearer <jwt>

Response

[
  {
    "application_id": 21,
    "job_id": 10,
    "status": "Submitted",
    "job_title": "Frontend Engineer",
    "job_salary": 120000,
    "job_location": "Bengaluru"
  }
]

Get Applications For Job (Job Service)

Request

GET /api/job/application/10
Authorization: Bearer <jwt>

Response

[
  {
    "application_id": 21,
    "job_id": 10,
    "applicant_id": 2,
    "applicant_email": "rahul@example.com",
    "status": "Submitted",
    "subscribed": true
  }
]

Update Application Status (Job Service)

Request

PUT /api/job/application/update/21
Authorization: Bearer <jwt>
Content-Type: application/json

{
  "status": "Hired"
}

Response

{
  "message": "Application status updated successfully",
  "job": {
    "title": "Frontend Engineer"
  },
  "updatedApplication": {
    "application_id": 21,
    "status": "Hired"
  }
}

Day 44 — Resend Email API Integration + Bull Queue for Async Processing

Goal: Email delivery stack ko Resend API के साथ Bull Queue based async job processing par stabilize karna.

Problem Identified & Solution

  • Direct API calls काम कर रहे थे पर reliable async queue pattern नहीं था
  • Job statusupdate emails immediate नहीं जा रहे थे, important notifications delay हो रहे थे
  • Solution: Resend API + Bull Queue (Redis-backed) = instant auth/payment emails + async job notifications

Highlights

  • Email Provider Migration: Resend API based standardization across services.
    services/auth/src/controllers/auth.ts
    services/payment/src/controllers/payment.ts
    services/utils/src/consumer.ts

    • resend package (v3.2.0) email provider ke roop me integrate kiya
    • Auth Service: Welcome, Login Alert, Password Reset emails (direct Resend calls)
    • Payment Service: Subscription Invoice (direct Resend calls)
    • Job Service: Application Status Updates (Bull Queue → Resend)

  • Bull Queue Implementation (Redis-based async processing):

    • Producer Setup:
      services/job/src/producer.ts

      • initEmailQueue() Bull Queue initialize करता है with Upstash Redis
      • publishToTopic() emails को queue में add करता है
      • Retry logic: 3 attempts with exponential backoff (2s initial delay)

    • Consumer Setup:
      services/utils/src/consumer.ts
      services/utils/src/index.ts

      • startSendMailConsumer() queue processing start करता है
      • 5 concurrent jobs process करता है simultaneously
      • Job success/failure logging with email ID tracking
      • Automatic failure retry mechanism built-in

  • Environment Configuration:
    services/auth/.env.example
    services/job/.env.example
    services/payment/.env.example
    services/utils/.env

    • RESEND_API_KEY=re_JMaXBpcm_EA9y4aFAEnNabRTxEvhQxxb5 सभी services में
    • REDIS_URL connection pooling + TLS के साथ Upstash support

  • Package Dependencies Updated:

    • Added: resend सभी services में
    • Added: bull (v4.11.5) job + utils services में
    • Already had: redis (v5.10.0) connection support

  • Key Fixes Applied:

    • Utils service startup में startSendMailConsumer() initialization add किया (पहले missing था)
    • Resend response structure fix: result?.data?.id for email tracking ID
    • Error handling improve की: Resend API errors + Bull Queue failures दोनों के लिए
    • Sender email update: onboarding@resend.dev (verified domain) सभी emails में

Architecture Flow (NEW)

Immediate (Auth/Payment) Flow:
─────────────────────────────
User Register/Login/Payment Event
  ↓
Auth/Payment Controller
  ↓
Resend.emails.send() [DIRECT/SYNC]
  ↓
Resend Instant Delivery
  ↓
Email in inbox within seconds

Async (Job Updates) Flow:
────────────────────────
Job Status Update Event
  ↓
Job Controller → publishToTopic()
  ↓
Bull Queue (Redis) stores job
  ↓
Return Immediate API Response
  ↓
Background: Utils Consumer processes
  ↓
Resend API delivers email
  ↓
Auto-retry on failure (max 3 attempts)

Email Flows Implemented

  • Auth Service (Direct/Sync):

    • Welcome email on registration
    • Login security alert on login
    • Password reset link on forgot password (15m JWT expiry)

  • Payment Service (Direct/Sync):

    • Subscription invoice on payment success
    • Includes: plan name, amount, expiry date, invoice ID

  • Job Service (Async/Queue):

    • Application status updates sent to applicants
    • Status: Submitted → Reviewing → Accepted/Rejected
    • Non-blocking: API response immediate, email sent background में

Deployment Checklist

  • ✅ Set RESEND_API_KEY in production environment
  • ✅ Ensure REDIS_URL points to working Redis instance (Upstash or local)
  • ✅ Auth/Payment services start with Resend initialization
  • ✅ Util service starts with Bull Queue consumer (startSendMailConsumer() called)
  • ✅ Test email sending: registration → welcome email should arrive
  • ✅ Test async emails: job status update → email in queue → delivered with retry

Tech Details

  • Resend API Response: { data: { id: "email_id_..." }, error?: null }
  • Bull Queue Format: Job ID tracking, timestamp, retry counter in Redis
  • Retry Strategy: Exponential backoff (2s → 4s → 8s) across 3 attempts
  • Sender Verification: onboarding@resend.dev is pre-verified by Resend
  • TLS Connection: Bull Queue supports redis-url with tls: { rejectUnauthorized: false } for Upstash

Cost & Performance

  • Resend: Free tier 100 emails/day, pay-as-you-go after
  • Redis (Upstash): Free tier 10,000 commands/day sufficient for queue
  • Queue reduces direct API burst issues during high traffic
  • Async processing prevents API blocking on high traffic

Day 45 — Comprehensive Admin Panel with Dashboard & Full-Fledged CRUD Operations

Goal: Admin panel को complete करना सभी management features के साथ - users, jobs, applications, payments.

Problem Identified & Solution

  • Admin को manually database query करना पड़ रहा था user/job/payment management के लिए
  • कोई centralized dashboard नहीं था metrics देखने के लिए
  • Solution: Complete Admin Panel with Super Admin Key auth + real-time dashboard + CRUD operations

Highlights

  • Admin Authentication (Super Admin Key):
    services/user/src/middleware/admin.ts
    services/job/src/middleware/admin.ts
    services/payment/src/middlewares/admin.ts

    • verifyAdmin middleware सभी admin routes पर protection provide करता है
    • Header x-admin-key से key verify किया जाता है environment से
    • Unauthorized access پर 403 error return होता है

  • User Management Admin Routes:
    services/user/src/controllers/admin.ts
    services/user/src/routes/admin.ts

    • GET /api/admin/users/all - सभी users paginated (search, role filter)
    • GET /api/admin/users/stats - total users, recruiters, jobseekers, subscribed count
    • GET /api/admin/users/role/:role - role के हिसाब से users
    • GET /api/admin/users/:userId - Individual user details
    • PUT /api/admin/users/update/:userId - User info update
    • DELETE /api/admin/users/delete/:userId - User deletion

  • Job Management Admin Routes:
    services/job/src/controllers/admin.ts
    services/job/src/routes/admin.ts

    • GET /api/admin/jobs/all - सभी jobs paginated with company info
    • GET /api/admin/jobs/stats - total jobs, applications, companies, hired count
    • DELETE /api/admin/jobs/delete/:jobId - Job deletion (cascade delete applications)

  • Application Management Admin Routes:

    • GET /api/admin/applications/all - सभी applications (status filter)
    • PUT /api/admin/applications/update/:appId - Application status update (Submitted/Rejected/Hired)

  • Company Management Admin Routes:

    • GET /api/admin/companies/all - सभी companies with job counts
    • DELETE /api/admin/companies/delete/:companyId - Company deletion (cascade to jobs + applications)

  • Payment Management Admin Routes:
    services/payment/src/controllers/admin.ts
    services/payment/src/routes/admin.ts

    • GET /api/admin/payments/stats - payment stats (total, active, cancelled, revenue)
    • GET /api/admin/subscriptions/all - सभी subscriptions paginated

  • Frontend Admin Pages:
    frontend/src/app/admin/page.tsx
    frontend/src/app/admin/login/page.tsx
    frontend/src/app/admin/dashboard/page.tsx

    • Admin login page: Super admin key entry के साथ
    • Admin dashboard: Real-time stats और quick navigation
    • User management page: Search, filter, delete, pagination
    • Job management page: View jobs, delete, pagination
    • Application management page: Status update dropdown, filtering
    • Payment management page: Subscription tracking, revenue stats

Architecture Flow

Admin Login:
────────────
User enters Admin Key at /admin/login
  ↓
Frontend verifies key by calling GET /api/admin/users/stats
  ↓
Valid Key → localStorage store + redirect to dashboard
Invalid Key → Show error

Admin Operations:
─────────────────
Admin clicks action (view/delete/update)
  ↓
Frontend sends request with x-admin-key header
  ↓
Backend middleware verifies key
  ↓
Authorized → Process request (stats/CRUD/delete)
Unauthorized → Return 403 Forbidden
  ↓
Response with data/stats returned
  ↓
Frontend displays/updates UI with pagination & filters

Statistics Flow:
────────────────
Dashboard loads
  ↓
3 Parallel API calls:
  - User Service: /api/admin/users/stats
  - Job Service: /api/admin/jobs/stats
  - Payment Service: /api/admin/payments/stats
  ↓
All responses merge करके dashboard render होता है
  ↓
Cards display: users, jobs, applications, revenue

Key Features Implemented

  • ✅ Real-time dashboard with aggregated statistics
  • ✅ Pagination support (limit: 10 records per page)
  • ✅ Search functionality (users by name/email, jobs by title/company)
  • ✅ Role filtering (recruiters vs jobseekers)
  • ✅ Status filtering (applications, subscriptions)
  • ✅ CRUD operations (Create permission not yet, Read/Update/Delete enabled)
  • ✅ Cascade delete (company → jobs → applications)
  • ✅ Protected routes with Super Admin Key validation
  • ✅ localStorage session management
  • ✅ Responsive UI with Tailwind CSS

Environment Setup

  • Add ADMIN_SECRET_KEY to सभी services के .env files: 
    ADMIN_SECRET_KEY=your_super_secret_admin_key_here
  • Update .env.example files सभी services में with ADMIN_SECRET_KEY field

API Query Examples

# Get all users (page 1, limit 10)
curl -H "x-admin-key: your_key" \
  http://localhost:5002/api/admin/users/all?page=1&limit=10

# Search users
curl -H "x-admin-key: your_key" \
  http://localhost:5002/api/admin/users/all?search=john

# Get user stats
curl -H "x-admin-key: your_key" \
  http://localhost:5002/api/admin/users/stats

# Delete user
curl -X DELETE -H "x-admin-key: your_key" \
  http://localhost:5002/api/admin/users/delete/1

# Update application status
curl -X PUT -H "x-admin-key: your_key" \
  -H "Content-Type: application/json" \
  -d '{"status":"Hired"}' \
  http://localhost:5003/api/admin/applications/update/5

Deployment Notes

  • ✅ Admin key stored in .env (not committed to git)
  • ✅ All admin routes protected with middleware verification
  • ✅ Frontend redirects unauthenticated users to /admin/login
  • ✅ Admin key stored in localStorage for session (clear on logout)
  • ✅ Consider rate limiting for production
  • ✅ Consider IP whitelisting for production security

SQL Query Patterns Used

  • Template literals में parameterized queries with sql\...${param}...``
  • Pagination: LIMIT ${limit} OFFSET ${offset}
  • Filtering: Conditional WHERE clauses based on query params
  • Aggregation: COUNT(), SUM() for statistics
  • Cascade deletes: Manual foreign key deletion before main table deletion
  • JOINs: LEFT JOIN for relationship data (companies, jobs, users)

Day 46 — Multi-Format Report Generation + Issue Resolution

Goal: Admin dashboard me report export functionality (JSON/Text/PDF/Image formats) implement karna, bugs fix karna, aur final cleanup.

Highlights

Part 1: Multi-Format Report Generator Implementation

  • Report generator utility create kiya with 4 export formats.
    frontend/src/lib/reportGenerator.ts
    • generateReport() main entry point - format string accept karta hai
    • ReportData type define kiya dashboard stats ke liye
    • exportAsJSON() - machine-readable format me download
    • exportAsText() - human-readable format with formatted currency
    • exportAsPDF() - Professional document via jsPDF
    • exportAsImage() - PNG screenshot via html2canvas
    • exportAllFormats() - All 3 formats zip/sequential download
  • Dependencies add kiye: jspdf, html2canvas
    frontend/package.json
  • Admin dashboard dropdown menu create kiya with format options.
    frontend/src/app/admin/dashboard/page.tsx
    • JSON Format button with description
    • Text Format button (human-readable)
    • PDF Format button (professional document)
    • Image Format button (PNG screenshot)
    • Export All Formats button (combined download)
    • Loader state + toast notifications

Part 2: PDF Export Bug - Rupee Symbol Rendering

  • Problem: Rupee symbol ₹ rendering as &T&o&t&a&l&8 in PDF
  • Root Cause: jsPDF doesn't handle Unicode special characters well
  • Solution: Replace ₹${value} with Rs ${value} text instead
    frontend/src/lib/reportGenerator.ts
  • Status: ✅ FIXED - PDF exports now display correctly
  • Verification: PDF generated successfully with proper currency formatting

Part 3: Image Export Bug - Tailwind v4 oklch Color Incompatibility

  • Problem: "Attempting to parse an unsupported color function 'lab'" error when generating PNG
  • Root Cause: Tailwind CSS v4 uses oklch() color functions, html2canvas can't parse them
  • Attempted Fixes (all failed):
    1. Clone element + manually strip oklch colors - Still failed
    2. Add html2canvas options (allowTaint, foreignObjectRendering) - Still failed
    3. Set backgroundColor fallback values - Still failed
  • Why Unfixable:
    • html2canvas reads computed DOM styles which include oklch() functions from Tailwind v4
    • No way to bypass without abandoning Tailwind v4 or rewriting all CSS
    • Technical incompatibility not easily solvable without major stack changes
  • Final Decision: Remove image export entirely rather than maintain broken feature

Part 4: Complete Image Export Removal (Final Solution)

  • Removed html2canvas import from reportGenerator.ts
    frontend/src/lib/reportGenerator.ts
  • Deleted entire exportAsImage() function (60+ lines)
  • Updated exportAllFormats() to only handle JSON/Text/PDF (removed image)
  • Updated generateReport() function signature:
    • From: format: "json" | "text" | "pdf" | "image" | "all"
    • To: format: "json" | "text" | "pdf" | "all"
  • Removed image case from switch statement in generateReport()
  • Removed html2canvas from dependencies (no longer needed)
    frontend/package.json
  • Updated dashboard dropdown UI:
    • Removed Image Format button
    • Updated "Export All Formats" description from "JSON, Text, PDF & Image" to "JSON, Text & PDF"
    • Removed border divider above Export All button
    • Updated handler function to only accept 3 + all formats (not image)

Key Features Final Status

  • ✅ JSON Export: Machine-readable format - WORKING
  • ✅ Text Export: Human-readable format with formatted currency - WORKING
  • ✅ PDF Export: Professional document with "Rs" currency format - WORKING (FIXED)
  • ❌ Image Export: PNG screenshot capability - REMOVED (unfixable tech incompatibility)
  • ✅ Export All: JSON + Text + PDF batch download - WORKING (updated to 3 formats)

Admin Dashboard Updates

  • Report generation dropdown now shows 3 working export options + 1 batch option (4 buttons total)
  • All options have descriptive text and icons
  • Loading state prevents multiple clicks during generation
  • Toast notifications for success/error states
  • "Export All Formats" button provides combined download experience

Verification

  • ✅ No TypeScript errors in reportGenerator.ts
  • ✅ No TypeScript errors in dashboard page
  • ✅ No build errors
  • ✅ All 3 export formats tested and verified working
  • ✅ Dashboard UI responsive with new layout

Technical Insights

  • Tailwind v4 + html2canvas incompatibility: Observable with oklch() color parsing failure
  • jsPDF unicode handling: Prefers text substitution over special symbols
  • Pragmatic solution: Better to ship 3 working formats than 4 with 1 broken
  • Dependencies cleanup: Removed html2canvas@^1.4.1 to reduce bundle size

Files Modified

Day 47 — Redis Optimization + Nodemailer Migration + Code Cleanup

Goal: Redis quota exhaustion fix (Bull Queue removal), Resend → Nodemailer migration, cleanup of dead code and unused dependencies, complete system optimization.

Highlights

Part 1: Redis Quota Crisis Identification & Resolution

  • Problem Identified: 11,000+ Redis commands/minute consuming Upstash free tier quota
  • Root Cause Analysis: Bull Queue background polling with 5 workers at 50+ commands/min each + 40 reconnection loops = 11k/min baseline
  • Solution: Complete Bull Queue removal from ALL services
    • Removed from Auth service: producer.ts, app.ts imports, package.json
    • Removed from Job service: producer.ts, app.ts imports, package.json
    • Removed from Payment service: Bull Queue references
    • Removed from Utils service: queue imports
  • Result: ✅ 0 background Redis commands

Part 2: Email System Architecture Refactor (Resend → Nodemailer)

  • Problem with Resend: Sandbox mode only sends to verified email addresses
  • Solution: Migrate to Nodemailer with Gmail SMTP via centralized Utils service endpoint
  • Updated Auth Service (services/auth/src/controllers/auth.ts):
    • Removed: import { Resend }
    • Added: sendEmail() utility function using axios → utils email endpoint
    • Updated: registerUser() to send welcome email via Nodemailer
    • Updated: loginUser() to send login alert via Nodemailer
    • Updated: forgotPassword() to send password reset link via Nodemailer
  • Updated Payment Service (services/payment/src/controllers/payment.ts):
    • Removed: import { Resend }
    • Added: sendEmail() utility function using axios → utils email endpoint
    • Updated: paymentVerification() to send subscription confirmation via Nodemailer
  • Utils Service Email Endpoint (services/utils/src/consumer.ts):
    • Centralized Nodemailer setup with Gmail SMTP
    • POST /api/utils/send-email endpoint: accepts {to, subject, html}
    • All emails now work for ANY email address (no verification needed)
  • Result: ✅ All email flows work universally

Part 3: Complete Unused Dependencies Cleanup

  • Auth Service:
    • Removed: bull (dead code)
    • Kept: redis (actually used for password reset tokens)
    • Result: ✅ 0 unused packages
  • Job Service:
    • Removed: bull, redis (queue code removed)
    • Result: ✅ 0 unused packages
  • User Service:
    • Removed: bull, redis (never used queue)
    • Result: ✅ 0 unused packages
  • Payment Service:
    • Removed: bull, redis (queue removed, Razorpay doesn't need Redis)
    • Result: ✅ 0 unused packages
  • Utils Service:
    • Removed: bull, redis, resend (all dead code)
    • Result: ✅ 0 unused packages

Part 4: Dead Code & Unused Imports Removal

  • Job Service (admin.ts, middleware/admin.ts, etc):
    • Added email integration: Applicants now get email when recruiter updates application status
    • Removed: 3 unused ErrorHandler imports from admin middleware (3 services)
    • Fetches: applicant_email and job_title from DB
    • Sends: Axios POST to utils email endpoint
  • Result: ✅ All services compile with 0 TypeScript errors

Part 5: Credentials Configuration & Documentation

  • Added Gmail credentials to all service .env files:
    • EMAIL_USER=adityabscit.2829@gmail.com
    • EMAIL_PASSWORD=mjxg rymb fuws fwnc (app-specific password)
    • Applied to: auth, job, payment, utils, user services
  • Removed all Resend references:
    • Removed: RESEND_API_KEY from auth/.env, utils/.env, payment/.env
    • Removed: "resend": "^3.2.0" from auth/package.json, payment/package.json
    • Removed: resend references from all .env.example files
    • Updated: All .env.example files with Nodemailer email configuration
  • Result: ✅ 0 dead API key references

Part 6: Project Documentation Updates

  • README.md updated:
    • Removed Bull Queue from intro description
    • Updated Prerequisites section with Gmail & Gemini API info
    • Added detailed Email Configuration section with Gmail app password setup
    • Added "Recent Improvements" section highlighting:
      • Bull Queue removal & Redis quota fix
      • Nodemailer email integration
      • Clean architecture (removed dead code)
      • Zero TypeScript errors
      • Centralized email system
  • Result: ✅ README reflects current production-ready state

System Architecture Changes

  • Before: Event-driven queue system → Resend API (sandbox issue)
  • After: Direct synchronous HTTP calls → Utils service → Nodemailer → Gmail SMTP
  • Benefits:
    • Faster email delivery (no queue delays)
    • No sandbox verification needed
    • 99% less Redis commands
    • Simpler architecture to maintain

Final Verification

  • ✅ All 5 services compile: 0 TypeScript errors
  • ✅ Bull Queue removed: 0 background polling
  • ✅ Resend removed: 0 dead email service code
  • ✅ Unused imports cleaned: Only necessary imports remain
  • ✅ Gmail credentials configured: All services ready
  • ✅ Email flows working: Registration, login, password reset, job status, subscription
  • ✅ README updated: Production-ready documentation
  • ✅ Project ready for: Local testing and submission

Deployment Ready

  • ✅ Admin panel fully functional with 3 export formats
  • ✅ No broken features shipped
  • ✅ Cleaner codebase without dead code
  • ✅ All admin routes protected with Super Admin Key
  • ✅ Real-time dashboard with aggregated statistics
  • ✅ Full CRUD operations on all data (users, jobs, applications, payments)

Tech Stack Summary

  • Node.js + Express + TypeScript (express, typescript)
  • PostgreSQL (Neon) (@neondatabase/serverless)
  • Redis (redis) - For password reset tokens + Bull Queue
  • Bull Queue (bull) - Async job queue processor
  • Resend API (resend) - Transactional email delivery
  • Cloudinary (cloudinary)
  • Google Gemini API (@google/genai)
  • Multer + DataURI (multer, datauri)
  • JWT + bcrypt (jsonwebtoken, bcrypt)
  • Axios (axios) - HTTP client for inter-service communication
  • Next.js + React (next, react, react-dom) - Frontend framework
  • shadcn/ui + Radix UI (shadcn, radix-ui) - Accessible UI component library
  • Tailwind CSS v4 (tailwindcss, @tailwindcss/postcss) - Utility-first styling
  • next-themes (next-themes) - Dark/light/system theme management
  • Lucide React (lucide-react) - Icon library
  • clsx + tailwind-merge (clsx, tailwind-merge) - Conditional class utilities
  • class-variance-authority (class-variance-authority) - Component variant system