ashwin/nxtgauge-backend-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
38 commits 3 branches 0 tags 1.3 MiB
Find a file
Ashwin Kumar 3716f60806 docs: add work implementation roadmap (wir.md) 
Full plan for completing all pending features across backend, frontend,
and admin. Includes Beeceptor mock payment endpoints, Wave 1-5 breakdown,
file-level implementation details, and parallelization strategy.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-06 22:26:45 +02:00
apps feat: add admin leads endpoint and fix routing 2026-04-06 19:23:47 +02:00
crates feat: complete backend implementation - payments service, admin endpoints, auth guards, submit-for-verification for all roles 2026-04-06 06:19:10 +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: complete backend implementation - payments service, admin endpoints, auth guards, submit-for-verification for all roles 2026-04-06 06:19:10 +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 chore: update service startup script 2026-04-06 01:47:10 +02:00
wir.md docs: add work implementation roadmap (wir.md) 2026-04-06 22:26:45 +02: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.