How petersem/gym works
Gym is a role-based fitness scheduling and booking application. Members and trainers use a mobile-first React app that calls the versioned JSON API: users authenticate, then browse sessions or bookings and perform role-allowed actions, including XML downloads. Guests can read/search blogs and register; members and trainers can manage blog posts and profiles. The backend also retains server-rendered page routes. Evidence for frontend-to-API behavior comes from the README and sampled frontend references; several API subsystems are represented by their existing directories because their implementation was not excerpted.
Main entry points: APIController.mjs API routing · api.mjs API client · DatabaseModel.mjs MySQL pool · UsersModel.mjs User records
Components 24
React app
- React routes
frontend/src/main.jsx - Authentication UI
frontend/src/authentication/useAuthenticate.jsx - API client
frontend/src/api.mjs - Timetable
frontend/src/sessions/TimetableView.jsx - Booking management
frontend/src/bookings/BookingListView.jsx - Blog views
frontend/src/blogs - Profile view
frontend/src/users/ProfileView.jsx
JSON API
- API routing
backend/src/controllers/api/APIController.mjs - API authentication
backend/src/controllers/api/APIAuthenticationController.mjs - User endpoints
backend/src/controllers/api - Session endpoints
backend/src/controllers/api/APISessionsController.mjs - Booking endpoints
backend/src/controllers/api/APIBookingsController.mjs - Blog endpoints
backend/src/controllers/api - Location endpoints
backend/src/controllers/api
Gym domain
- User records
backend/src/models/UsersModel.mjs - Session records
backend/src/models/SessionsModel.mjs - Booking records
backend/src/models/BookingsModel.mjs - Activity records
backend/src/models/ActivitiesModel.mjs - Location records
backend/src/models/LocationModel.mjs - MySQL pool
backend/src/models/DatabaseModel.mjs - Blog records
backend/src/models/BlogModel.mjs
Server-rendered app
- Page controllers
backend/src/controllers - Browser authentication
backend/src/controllers/AuthenticationController.mjs
Other components
- Visitor
Connections 30
- Visitor → React routes: uses
- React routes → Authentication UI: renders
frontend/src/main.jsx - Authentication UI → API client: requests
frontend/src/authentication/useAuthenticate.jsx - Timetable → API client: requests
frontend/src/sessions/TimetableView.jsx - Booking management → API client: requests
- Blog views → API client: requests
- Profile view → API client: requests
frontend/src/users/ProfileView.jsx - API client → API routing: calls
- API routing → API authentication: routes
backend/src/controllers/api/APIController.mjs - API routing → User endpoints: routes
backend/src/controllers/api/APIController.mjs - API routing → Session endpoints: routes
backend/src/controllers/api/APIController.mjs - API routing → Booking endpoints: routes
backend/src/controllers/api/APIController.mjs - API routing → Blog endpoints: routes
backend/src/controllers/api/APIController.mjs - API routing → Location endpoints: routes
backend/src/controllers/api/APIController.mjs - API authentication → User records: reads/writes
backend/src/controllers/api/APIAuthenticationController.mjs - Session endpoints → Session records: queries
backend/src/controllers/api/APISessionsController.mjs - Booking endpoints → Booking records: queries
backend/src/controllers/api/APIBookingsController.mjs - Booking endpoints → Session records: checks
backend/src/controllers/api/APIBookingsController.mjs - User endpoints → User records: manages
backend/src/controllers/api/APIAuthenticationController.mjs - Location endpoints → Location records: manages
backend/src/controllers/api/APISessionsController.mjs - Blog endpoints → Blog records: manages
- User records → MySQL pool: queries
backend/src/models/UsersModel.mjs - Session records → MySQL pool: queries
backend/src/models/SessionsModel.mjs - Booking records → MySQL pool: queries
backend/src/models/BookingsModel.mjs - Activity records → MySQL pool: queries
backend/src/models/ActivitiesModel.mjs - Location records → MySQL pool: queries
backend/src/models/LocationModel.mjs - Blog records → MySQL pool: queries
- Visitor → Page controllers: uses
- Page controllers → Browser authentication: authenticates
backend/src/server.mjs - Browser authentication → User records: authenticates against
backend/src/controllers/AuthenticationController.mjs