d2754db37706a14a855f74dd800769b843033823
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
## Overview
Complete architectural overhaul merging dual event systems into a unified activity model
with multi-VIP support, enhanced search capabilities, and improved UX throughout.
## Database & Schema Changes
### Unified Activity Model (Breaking Change)
- Merged Event/EventTemplate/EventAttendance into single ScheduleEvent model
- Dropped duplicate tables: Event, EventAttendance, EventTemplate
- Single source of truth for all activities (transport, meals, meetings, events)
- Migration: 20260131180000_drop_duplicate_event_tables
### Multi-VIP Support (Breaking Change)
- Changed schema from single vipId to vipIds array (String[])
- Enables multiple VIPs per activity (ridesharing, group events)
- Migration: 20260131122613_multi_vip_support
- Updated all backend services to handle multi-VIP queries
### Seed Data Updates
- Rebuilt seed.ts with unified activity model
- Added multi-VIP rideshare examples (3 VIPs in SUV, 4 VIPs in van)
- Includes mix of transport + non-transport activities
- Balanced VIP test data (50% OFFICE_OF_DEVELOPMENT, 50% ADMIN)
## Backend Changes
### Services Cleanup
- Removed deprecated common-events endpoints
- Updated EventsService for multi-VIP support
- Enhanced VipsService with multi-VIP activity queries
- Updated DriversService, VehiclesService for unified model
- Added add-vips-to-event.dto for bulk VIP assignment
### Abilities & Permissions
- Updated ability.factory.ts: Event → ScheduleEvent subject
- Enhanced guards for unified activity permissions
- Maintained RBAC (Administrator, Coordinator, Driver roles)
### DTOs
- Updated create-event.dto: vipId → vipIds array
- Updated update-event.dto: vipId → vipIds array
- Added add-vips-to-event.dto for bulk operations
- Removed obsolete event-template DTOs
## Frontend Changes
### UI/UX Improvements
**Renamed "Schedule" → "Activities" Throughout**
- More intuitive terminology for coordinators
- Updated navigation, page titles, buttons
- Changed "Schedule Events" to "Activities" in Admin Tools
**Activities Page Enhancements**
- Added comprehensive search bar (searches: title, location, description, VIP names, driver, vehicle)
- Added sortable columns: Title, Type, VIPs, Start Time, Status
- Visual sort indicators (↑↓ arrows)
- Real-time result count when searching
- Empty state with helpful messaging
**Admin Tools Updates**
- Balanced VIP test data: 10 OFFICE_OF_DEVELOPMENT + 10 ADMIN
- More BSA-relevant organizations (Coca-Cola, AT&T, Walmart vs generic orgs)
- BSA leadership titles (National President, Chief Scout Executive, Regional Directors)
- Relabeled "Schedule Events" → "Activities"
### Component Updates
**EventList.tsx (Activities Page)**
- Added search state management with real-time filtering
- Implemented multi-field sorting with direction toggle
- Enhanced empty states for search + no data scenarios
- Filter tabs + search work together seamlessly
**VIPSchedule.tsx**
- Updated for multi-VIP schema (vipIds array)
- Shows complete itinerary timeline per VIP
- Displays all activities for selected VIP
- Groups by day with formatted dates
**EventForm.tsx**
- Updated to handle vipIds array instead of single vipId
- Multi-select VIP assignment
- Maintains backward compatibility
**AdminTools.tsx**
- New balanced VIP test data (10/10 split)
- BSA-context organizations
- Updated button labels ("Add Test Activities")
### Routing & Navigation
- Removed /common-events routes
- Updated navigation menu labels
- Maintained protected route structure
- Cleaner URL structure
## New Features
### Multi-VIP Activity Support
- Activities can have multiple VIPs (ridesharing, group events)
- Efficient seat utilization tracking (3/6 seats, 4/12 seats)
- Better coordination for shared transport
### Advanced Search & Filtering
- Full-text search across multiple fields
- Instant filtering as you type
- Search + type filters work together
- Clear visual feedback (result counts)
### Sortable Data Tables
- Click column headers to sort
- Toggle ascending/descending
- Visual indicators for active sort
- Sorts persist with search/filter
### Enhanced Admin Tools
- One-click test data generation
- Realistic BSA Jamboree scenario data
- Balanced department representation
- Complete 3-day itineraries per VIP
## Testing & Validation
### Playwright E2E Tests
- Added e2e/ directory structure
- playwright.config.ts configured
- PLAYWRIGHT_GUIDE.md documentation
- Ready for comprehensive E2E testing
### Manual Testing Performed
- Multi-VIP activity creation ✓
- Search across all fields ✓
- Column sorting (all fields) ✓
- Filter tabs + search combination ✓
- Admin Tools data generation ✓
- Database migrations ✓
## Breaking Changes & Migration
**Database Schema Changes**
1. Run migrations: `npx prisma migrate deploy`
2. Reseed database: `npx prisma db seed`
3. Existing data incompatible (dev environment - safe to nuke)
**API Changes**
- POST /events now requires vipIds array (not vipId string)
- GET /events returns vipIds array
- GET /vips/:id/schedule updated for multi-VIP
- Removed /common-events/* endpoints
**Frontend Type Changes**
- ScheduleEvent.vipIds: string[] (was vipId: string)
- EventFormData updated accordingly
- All pages handle array-based VIP assignment
## File Changes Summary
**Added:**
- backend/prisma/migrations/20260131180000_drop_duplicate_event_tables/
- backend/src/events/dto/add-vips-to-event.dto.ts
- frontend/src/components/InlineDriverSelector.tsx
- frontend/e2e/ (Playwright test structure)
- Documentation: NAVIGATION_UX_IMPROVEMENTS.md, PLAYWRIGHT_GUIDE.md
**Modified:**
- 30+ backend files (schema, services, DTOs, abilities)
- 20+ frontend files (pages, components, types)
- Admin tools, seed data, navigation
**Removed:**
- Event/EventAttendance/EventTemplate database tables
- Common events frontend pages
- Obsolete event template DTOs
## Next Steps
**Pending (Phase 3):**
- Activity Templates for bulk event creation
- Operations Dashboard (today's activities + conflicts)
- Complete workflow testing with real users
- Additional E2E test coverage
## Notes
- Development environment - no production data affected
- Database can be reset anytime: `npx prisma migrate reset`
- All servers tested and running successfully
- HMR working correctly for frontend changes
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
VIP Coordinator
A comprehensive VIP transportation coordination system built with React, Node.js, PostgreSQL, and Redis. This application provides real-time scheduling, driver management, and VIP coordination capabilities with enterprise-grade security and scalability.
🚀 Quick Start with Docker
Prerequisites
- Docker and Docker Compose installed
- Google OAuth credentials (for authentication)
- Domain name or localhost for development
1. Pull the Images
docker pull t72chevy/vip-coordinator:backend-latest
docker pull t72chevy/vip-coordinator:frontend-latest
2. Create Environment File
Create a .env file in your project directory:
# Database Configuration
POSTGRES_DB=vip_coordinator
POSTGRES_USER=vip_user
POSTGRES_PASSWORD=your_secure_password_here
# Backend Configuration
DATABASE_URL=postgresql://vip_user:your_secure_password_here@postgres:5432/vip_coordinator
NODE_ENV=production
PORT=3000
# Frontend Configuration
VITE_API_URL=http://localhost:3000
VITE_FRONTEND_URL=http://localhost
# Google OAuth Configuration
GOOGLE_CLIENT_ID=your_google_client_id_here
GOOGLE_CLIENT_SECRET=your_google_client_secret_here
# Redis Configuration
REDIS_URL=redis://redis:6379
# Security
JWT_SECRET=auto-generated-on-startup
3. Create Docker Compose File
Create a docker-compose.yml file:
version: '3.8'
services:
postgres:
image: postgres:15-alpine
environment:
POSTGRES_DB: ${POSTGRES_DB}
POSTGRES_USER: ${POSTGRES_USER}
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
volumes:
- postgres_data:/var/lib/postgresql/data
ports:
- "5432:5432"
healthcheck:
test: ["CMD-SHELL", "pg_isready -U ${POSTGRES_USER} -d ${POSTGRES_DB}"]
interval: 10s
timeout: 5s
retries: 5
redis:
image: redis:7-alpine
ports:
- "6379:6379"
healthcheck:
test: ["CMD", "redis-cli", "ping"]
interval: 10s
timeout: 5s
retries: 5
backend:
image: t72chevy/vip-coordinator:backend-latest
environment:
- DATABASE_URL=${DATABASE_URL}
- NODE_ENV=${NODE_ENV}
- PORT=${PORT}
- GOOGLE_CLIENT_ID=${GOOGLE_CLIENT_ID}
- GOOGLE_CLIENT_SECRET=${GOOGLE_CLIENT_SECRET}
- REDIS_URL=${REDIS_URL}
- JWT_SECRET=${JWT_SECRET}
ports:
- "3000:3000"
depends_on:
postgres:
condition: service_healthy
redis:
condition: service_healthy
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:3000/health"]
interval: 30s
timeout: 10s
retries: 3
frontend:
image: t72chevy/vip-coordinator:frontend-latest
environment:
- VITE_API_URL=${VITE_API_URL}
- VITE_FRONTEND_URL=${VITE_FRONTEND_URL}
ports:
- "80:80"
depends_on:
backend:
condition: service_healthy
volumes:
postgres_data:
4. Deploy the Application
# Start all services
docker-compose up -d
# Check service status
docker-compose ps
# View logs
docker-compose logs -f
5. Access the Application
- Frontend: http://localhost
- Backend API: http://localhost:3001
- Health Check: http://localhost:3001/health
🔧 Configuration
Google OAuth Setup
- Go to the Google Cloud Console
- Create a new project or select an existing one
- Enable the Google+ API
- Create OAuth 2.0 credentials
- Add your domain to authorized origins
- Add your callback URL:
http://your-domain/auth/google/callback
Environment Variables
| Variable | Description | Required | Default |
|---|---|---|---|
POSTGRES_DB |
PostgreSQL database name | Yes | vip_coordinator |
POSTGRES_USER |
PostgreSQL username | Yes | vip_user |
POSTGRES_PASSWORD |
PostgreSQL password | Yes | - |
DATABASE_URL |
Full database connection string | Yes | - |
GOOGLE_CLIENT_ID |
Google OAuth client ID | Yes | - |
GOOGLE_CLIENT_SECRET |
Google OAuth client secret | Yes | - |
REDIS_URL |
Redis connection string | Yes | redis://redis:6379 |
NODE_ENV |
Node.js environment | No | production |
PORT |
Backend server port | No | 3001 |
VITE_API_URL |
Frontend API URL | Yes | - |
VITE_FRONTEND_URL |
Frontend base URL | Yes | - |
🏗️ Architecture
Services
- Frontend: React application with Vite build system, served by Nginx
- Backend: Node.js/Express API server with TypeScript
- Database: PostgreSQL for persistent data storage
- Cache: Redis for session management and real-time features
Security Features
- JWT Auto-Rotation: Automatic JWT secret rotation for enhanced security
- Google OAuth: Secure authentication via Google
- Non-Root Containers: All containers run as non-root users
- Health Checks: Comprehensive health monitoring
- Input Validation: Robust input validation and sanitization
Key Features
- Real-time Scheduling: Live updates for VIP schedules and assignments
- Driver Management: Comprehensive driver tracking and assignment
- User Roles: Admin and driver role-based access control
- Responsive Design: Mobile-friendly interface
- Data Export: Export capabilities for schedules and reports
- Audit Logging: Comprehensive activity logging
🔍 Monitoring & Troubleshooting
Health Checks
# Check all services
docker-compose ps
# Backend health
curl http://localhost:3001/health
# View logs
docker-compose logs backend
docker-compose logs frontend
docker-compose logs postgres
docker-compose logs redis
Common Issues
-
Database Connection Issues
- Ensure PostgreSQL is healthy:
docker-compose logs postgres - Verify DATABASE_URL format
- Check password special characters (avoid
!and other special chars)
- Ensure PostgreSQL is healthy:
-
Google OAuth Issues
- Verify client ID and secret
- Check authorized origins in Google Console
- Ensure callback URL matches your domain
-
Frontend Not Loading
- Check VITE_API_URL points to correct backend
- Verify backend is healthy
- Check browser console for errors
🚀 Production Deployment
For Production Use
- Use HTTPS: Configure SSL/TLS certificates
- Secure Passwords: Use strong, unique passwords
- Environment Secrets: Use Docker secrets or external secret management
- Backup Strategy: Implement regular database backups
- Monitoring: Set up application and infrastructure monitoring
- Load Balancing: Consider load balancers for high availability
Example Production Environment
# Production environment example
POSTGRES_PASSWORD=super_secure_random_password_here
VITE_API_URL=https://api.yourdomain.com
VITE_FRONTEND_URL=https://yourdomain.com
NODE_ENV=production
📝 API Documentation
Authentication Endpoints
GET /auth/google- Initiate Google OAuthGET /auth/google/callback- OAuth callbackPOST /auth/logout- Logout userGET /auth/me- Get current user
Core Endpoints
GET /api/vips- List VIPsPOST /api/vips- Create VIPGET /api/drivers- List driversPOST /api/drivers- Create driverGET /api/schedules- List schedulesPOST /api/schedules- Create schedule
Health & Status
GET /health- Application health checkGET /api/status- Detailed system status
🤝 Contributing
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests if applicable
- Submit a pull request
📄 License
This project is licensed under the MIT License - see the LICENSE file for details.
🆘 Support
For issues and questions:
- Check the troubleshooting section above
- Review Docker Compose logs
- Create an issue on GitHub with:
- Docker Compose version
- Environment details
- Error logs
- Steps to reproduce
🔄 Updates
To update to the latest version:
# Pull latest images
docker-compose pull
# Restart services
docker-compose up -d
Built with ❤️ for efficient VIP transportation coordination
Description
Languages
TypeScript
96.4%
JavaScript
1.2%
Shell
1.2%
CSS
0.5%
Dockerfile
0.3%
Other
0.3%