saqib mirandClaude Sonnet 5 7948182988 feat(012-admin-list-views): add GET /admin/products/:id/knowledge for governance
Follow-up to 012-admin-list-views, discovered while building supporthub-
web's own knowledge-governance screen (001-agent-admin-ui User Story 7):
GET /knowledge/retrieve only ever returns published entries (its own
AI-consumption purpose), so a governance screen that needs to see and
publish a draft entry had no endpoint to list it. Adds a small
admin-list-views-style read query scoped to the knowledge module itself.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-07 16:35:25 +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%