How anuragahirwar958-prog/eventflex works
Eventflex is an event-staffing marketplace: organizers publish events and staffing jobs, while workers can browse live jobs and apply. The visible backend workflow validates requests in tRPC routers and delegates job, event, and application operations to database code. The client exposes a home route and shared API/auth plumbing. The tree also includes map and AI-chat UI and several integration modules, but their runtime wiring is not shown in the sampled source, so those links are left out.
Main entry points: index.ts Server entry · routers.ts App router · main.tsx tRPC client · Home.tsx Home page
Components 16
Client application
- Home page
client/src/pages/Home.tsx - Map UI
client/src/components/Map.tsx - AI chat UI
client/src/components/AIChatBox.tsx - Auth hook
client/src/_core/hooks/useAuth.ts - tRPC client
client/src/main.tsx
API and auth
- App router
server/routers.ts - Server entry
server/_core/index.ts - Request context
server/_core/context.ts - OAuth routes
server/_core/oauth.ts - System router
server/_core/systemRouter.ts - Owner notification
server/_core/notification.ts
Marketplace data
- Marketplace operations
server/db.ts - Database schema
drizzle/schema.ts
Other components
- Marketplace user
- MySQL database
- OAuth provider
Connections 13
- Marketplace user → Home page: uses
- Home page → tRPC client: requests data
- Auth hook → tRPC client: queries auth
- tRPC client → Server entry: sends API calls
- Server entry → App router: dispatches API
- Server entry → Request context: creates context
- Server entry → OAuth routes: registers routes
- OAuth routes → OAuth provider: authenticates
- App router → Marketplace operations: runs marketplace operations
- Marketplace operations → MySQL database: reads and writes
- Database schema → MySQL database: defines stored data
- App router → System router: mounts system routes
- System router → Owner notification: calls notification