Major Enhancement: NestJS Migration + CASL Authorization + Error Handling
Some checks failed
CI/CD Pipeline / Backend Tests (push) Has been cancelled
CI/CD Pipeline / Frontend Tests (push) Has been cancelled
CI/CD Pipeline / Build Docker Images (push) Has been cancelled
CI/CD Pipeline / Security Scan (push) Has been cancelled
CI/CD Pipeline / Deploy to Staging (push) Has been cancelled
CI/CD Pipeline / Deploy to Production (push) Has been cancelled

Complete rewrite from Express to NestJS with enterprise-grade features:

## Backend Improvements
- Migrated from Express to NestJS 11.0.1 with TypeScript
- Implemented Prisma ORM 7.3.0 for type-safe database access
- Added CASL authorization system replacing role-based guards
- Created global exception filters with structured logging
- Implemented Auth0 JWT authentication with Passport.js
- Added vehicle management with conflict detection
- Enhanced event scheduling with driver/vehicle assignment
- Comprehensive error handling and logging

## Frontend Improvements
- Upgraded to React 19.2.0 with Vite 7.2.4
- Implemented CASL-based permission system
- Added AbilityContext for declarative permissions
- Created ErrorHandler utility for consistent error messages
- Enhanced API client with request/response logging
- Added War Room (Command Center) dashboard
- Created VIP Schedule view with complete itineraries
- Implemented Vehicle Management UI
- Added mock data generators for testing (288 events across 20 VIPs)

## New Features
- Vehicle fleet management (types, capacity, status tracking)
- Complete 3-day Jamboree schedule generation
- Individual VIP schedule pages with PDF export (planned)
- Real-time War Room dashboard with auto-refresh
- Permission-based navigation filtering
- First user auto-approval as administrator

## Documentation
- Created CASL_AUTHORIZATION.md (comprehensive guide)
- Created ERROR_HANDLING.md (error handling patterns)
- Updated CLAUDE.md with new architecture
- Added migration guides and best practices

## Technical Debt Resolved
- Removed custom authentication in favor of Auth0
- Replaced role checks with CASL abilities
- Standardized error responses across API
- Implemented proper TypeScript typing
- Added comprehensive logging

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
2026-01-31 08:50:25 +01:00
parent 8ace1ab2c1
commit 868f7efc23
351 changed files with 44997 additions and 6276 deletions

33
SUPABASE_MIGRATION.md Normal file
View File

@@ -0,0 +1,33 @@
# Supabase Auth Migration Plan
## Why Supabase?
-**Self-hosted Docker** - Full control, no external dependencies
-**Built-in Auth** - JWT tokens, social login (Google), user management
-**Simple API** - Similar to Auth0 but simpler
-**PostgreSQL** - Uses your existing database
-**React SDK** - Easy frontend integration
-**No Tailwind issues** - Doesn't affect frontend build
## Migration Steps
### 1. Add Supabase to Docker Compose
- Add Supabase services (Auth API, PostgREST, GoTrue)
- Configure to use existing PostgreSQL database
- Set up environment variables
### 2. Update Backend
- Replace Auth0 SDK with Supabase client
- Update JWT validation to use Supabase keys
- Simplify auth routes
### 3. Update Frontend
- Replace `@auth0/auth0-react` with `@supabase/supabase-js`
- Update Login component
- Update App.tsx auth logic
### 4. Database Migration
- Keep existing user table structure
- Add Supabase auth tables (if needed)
- Map `auth0_sub``supabase_user_id`
## Estimated Time: 30-45 minutes