How grigxy/fitness-assistant works
Fitness Assistant is a REST-backed fitness tracker for nutrition, hydration, workouts, progress, and motivation, with a built-in static browser frontend. The user workflow is browser/API use through controllers into domain use cases, with persistence behind repository ports. The README documents additional capabilities such as targets, favorites, sharing, admin management, and JWT authentication. Source excerpts are limited to the frontend API helper, so implementation links beyond its shown requests are omitted or marked unverified.
Main entry points: controller REST controllers · repository Repository ports · api.js API client · user Accounts and profiles
Components 19
Browser frontend
- API client
src/main/resources/static/js/api.js - Browser
HTTP and security
- Authentication
src/main/java/com/example/fitness_assistant/web/controller/AuthController.java - REST controllers
src/main/java/com/example/fitness_assistant/web/controller - JWT security
src/main/java/com/example/fitness_assistant/infrastructure/security
Fitness workflows
- Accounts and profiles
src/main/java/com/example/fitness_assistant/application/service/user - Targets and streaks
src/main/java/com/example/fitness_assistant/application/service/targets - Food and meals
src/main/java/com/example/fitness_assistant/application/service/food - Hydration log
src/main/java/com/example/fitness_assistant/application/service/hydration - Weight tracking
src/main/java/com/example/fitness_assistant/application/service/bodyweight - Workout plans
src/main/java/com/example/fitness_assistant/application/service/workout - Workout sessions
src/main/java/com/example/fitness_assistant/application/service/workoutsession - Exercise catalog
src/main/java/com/example/fitness_assistant/application/service/exercise - Workout sharing
src/main/java/com/example/fitness_assistant/application/service/workoutaccess - Favorites
src/main/java/com/example/fitness_assistant/application/service/favoritefood
Persistence
- Repository ports
src/main/java/com/example/fitness_assistant/core/repository - JPA adapters
src/main/java/com/example/fitness_assistant/infrastructure/adapter - PostgreSQL data
src/main/java/com/example/fitness_assistant/infrastructure/persistence
Other components
- Fitness user
Connections 28
- Fitness user → Browser: uses
README.md - Browser → API client: loads
README.md - API client → REST controllers: calls API
src/main/resources/static/js/api.js - API client → Authentication: deletes account
src/main/resources/static/js/api.js - REST controllers → Accounts and profiles: dispatches
README.md - REST controllers → Targets and streaks: dispatches
README.md - REST controllers → Food and meals: dispatches
README.md - REST controllers → Hydration log: dispatches
README.md - REST controllers → Weight tracking: dispatches
README.md - REST controllers → Workout plans: dispatches
README.md - REST controllers → Workout sessions: dispatches
README.md - REST controllers → Exercise catalog: dispatches
README.md - REST controllers → Workout sharing: dispatches
README.md - REST controllers → Favorites: dispatches
README.md - Authentication → Accounts and profiles: authenticates
README.md - JWT security → REST controllers: secures
README.md - Accounts and profiles → Repository ports: uses
README.md - Targets and streaks → Repository ports: uses
README.md - Food and meals → Repository ports: uses
README.md - Hydration log → Repository ports: uses
README.md - Weight tracking → Repository ports: uses
README.md - Workout plans → Repository ports: uses
README.md - Workout sessions → Repository ports: uses
README.md - Exercise catalog → Repository ports: uses
README.md - Workout sharing → Repository ports: uses
README.md - Favorites → Repository ports: uses
README.md - JPA adapters → Repository ports: implements
README.md - JPA adapters → PostgreSQL data: persists
README.md