ashwin/nxtgauge-backend-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
21 commits 3 branches 0 tags 1.3 MiB
Find a file
Ashwin Kumar 96f9da2cdb feat: add KB and support ticket system 
- 2 new migrations: summary/tags columns on kb_articles, description/requester fields on support_tickets
- handlers/kb.rs: public routes (GET /api/kb/categories|articles|articles/:slug) + admin CRUD (/api/admin/kb/*)
- handlers/support.rs: user ticket routes + admin support-cases CRUD with internal notes
- Registered all new routes in users service main.rs
- Gateway resolve_upstream: /api/kb/*, /api/support/*, /api/admin/kb/*, /api/admin/support-cases/* → users service
- scripts/seed_kb.sql: 8 categories, 28 full-length published articles covering all user roles

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-02 13:36:12 +02:00
apps feat: add KB and support ticket system 2026-04-02 13:36:12 +02:00
crates feat: add KB and support ticket system 2026-04-02 13:36:12 +02:00
docs chore: bootstrap rust backend workspace and migration master plan 2026-03-16 22:23:58 +01:00
scripts feat: add KB and support ticket system 2026-04-02 13:36:12 +02:00
.env.example feat(backend): enforce profile approvals and complete migration approval flows 2026-03-19 00:30:23 +01:00
.gitignore feat: add Redis for OTP, auth tokens, rate limiting, lead dedup and marketplace cache 2026-03-18 22:58:42 +01:00
Cargo.toml feat(admin): wire management modules to live backend and add UGC role 2026-04-02 13:09:43 +02:00
docker-compose.yml feat: complete rust microservices migration with real db logic 2026-03-17 20:42:51 +01:00
README.md chore: bootstrap rust backend workspace and migration master plan 2026-03-16 22:23:58 +01:00
start-services.sh Fix environment variable exports in start-services 2026-03-26 00:36:14 +01:00

README.md

NXTGAUGE Backend Rust

Rust migration target for nxtgauge-nov-2025-backend, preserving the same microservices and request flow.

Target Service Topology

  • gateway (HTTP API)
  • users (identity, runtime roles, onboarding, approvals)
  • companies
  • customers
  • professionals
  • jobseekers

Migration Policy

  • Keep contracts stable (REST + proto semantics).
  • Keep runtime-config and onboarding schema behavior unchanged during parity phases.
  • Replace service implementations one by one.

See docs/MIGRATION_MASTER_PLAN.md for full staged plan.