saqib mirandClaude Sonnet 5 d58bc98c7f docs(011-agent-ticket-queue): spec for agent-user linking and assigned-ticket listing
Discovered while starting supporthub-web's 001-agent-admin-ui planning:
its agent-dashboard user story needs to list tickets currently assigned
to an agent, and no such query exists anywhere in the ticketing or
orchestration modules. Also finishes wiring Agent.userId (added in
010-identity-auth as schema-only, never consumed by any workflow) so a
logged-in session can resolve to its own agent roster row at all.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-07 12:55:41 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-20 11:27:15 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30
fix
2026-09-03 16:48:27 +05:30
2026-08-19 16:29:17 +05:30
2026-08-19 16:29:17 +05:30

SupportHub API

Development (Docker)

  • Start all services: docker compose --env-file .env.development -f docker-compose.development.yml up -d --build
  • Start only database & cache (for local app development): docker compose --env-file .env.development -f docker-compose.development.yml up -d postgres redis

Test (Docker)

  • docker compose --env-file .env.test -f docker-compose.test.yml up --build

Production (Docker)

  • docker compose --env-file .env.prod -f docker-compose.prod.yml up --build -d

Stop / Down

  • Stop production: docker compose -f docker-compose.prod.yml down
  • Stop development: docker compose -f docker-compose.development.yml down
  • Stop development & wipe volumes: docker compose --env-file .env.development -f docker-compose.development.yml down -v

List Containers & Logs

  • List containers: docker compose --env-file .env.development -f docker-compose.development.yml ps
  • Follow logs: docker compose --env-file .env.development -f docker-compose.development.yml logs -f

Local Development (Host)

  1. Start database & cache in Docker:
    docker compose --env-file .env.development -f docker-compose.development.yml up -d postgres redis
    
  2. Start API server in watch mode:
    npm run dev
    

Database Migrations & Prisma

  • Generate Prisma Client:

    npm run prisma:generate
    
  • Run / Apply Dev Migrations:

    npx dotenv-cli -e .env.development -- npm run prisma:migrate
    
  • Deploy Migrations (Production/CI):

    npx dotenv-cli -e .env.development -- npm run prisma:deploy
    
  • Push Schema directly (Sync schema without migration files):

    npx dotenv-cli -e .env.development -- npx prisma db push
    

Database Seeding

  • Seed Database (Roles, Products, Categories, Hierarchy & Demo data):
    npx dotenv-cli -e .env.development -- npm run prisma:seed
    
S
Description
No description provided
Readme
1.2 MiB
Languages
TypeScript 93.2%
PowerShell 6.5%
JavaScript 0.2%