ashwin/nxtgauge-backend-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
26 commits 3 branches 0 tags 1.3 MiB
Find a file
Ashwin Kumar 5451ff5657 Fix users service startup panic — route syntax and admin login 
- All /:param routes converted to /{param} (Axum v0.8 breaking change)
- admin.rs, kb.rs, reviews.rs, support.rs, pricing.rs, coupons.rs fixed
- employees app routes fixed (departments, designations, employees handlers)
- kb.rs multiline route definitions also fixed
- Users service now boots successfully

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-03 02:32:46 +02:00
apps Fix users service startup panic — route syntax and admin login 2026-04-03 02:32:46 +02:00
crates Fix backend compile errors after schema migrations 2026-04-03 02:25:47 +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.