How anepchidi/tyler-made-fitness works
This is a workout and fitness tracking application: users sign in, record workouts, and review history and progress, with nutrition, templates, and social sharing as additional capabilities. The React app routes users to feature views through App and a shared API client; FastAPI routers handle feature requests and use SQLAlchemy models for persistence. The nutrition router also integrates with FatSecret. The README is empty, so feature scope comes from the source index and sampled code; unsampled frontend and router details are represented only where the index supports their existence, not speculative call paths.
Main entry points: App.jsx App navigation · main.py HTTP application · client.js API client · dependencies.py Auth and DB dependencies
Components 27
Frontend
- App navigation
frontend/src/App.jsx - Sign-in view
frontend/src/components/AuthPage.jsx - Workout logging
frontend/src/components/WorkoutLogger.jsx - Dashboard
frontend/src/components/Dashboard.jsx - Workout history
frontend/src/components/History.jsx - Exercise analytics
frontend/src/components/ExerciseAnalytics.jsx - Workout templates
frontend/src/components/Templates.jsx - Nutrition tracking
frontend/src/components/Nutrition.jsx - Profile settings
frontend/src/components/Profile.jsx - Social feed
frontend/src/components/SocialFeed.jsx - Food presets
frontend/src/data/presets.js - API client
frontend/src/api/client.js
Backend API
- HTTP application
backend/main.py - Authentication
backend/routers/auth.py - Exercise library
backend/routers/library.py - Workout records
backend/routers/workouts.py - Template and progress
backend/routers/templates.py - Nutrition service
backend/routers/nutrition.py - Account settings
backend/routers/settings.py - Social features
backend/routers/social.py
Domain and persistence
- Request schemas
backend/schemas.py - Auth and DB dependencies
backend/dependencies.py - Domain models
backend/models.py - Relational database
backend/database.py - Runtime configuration
backend/config.py
External services
- FatSecret API
Other components
- User
Connections 48
- User → App navigation: uses
frontend/src/App.jsx - App navigation → Sign-in view: renders
frontend/src/App.jsx - App navigation → Dashboard: renders
frontend/src/App.jsx - App navigation → Workout logging: renders
frontend/src/App.jsx - App navigation → Workout history: renders
frontend/src/App.jsx - App navigation → Exercise analytics: renders
frontend/src/App.jsx - App navigation → Workout templates: renders
frontend/src/App.jsx - App navigation → Nutrition tracking: renders
frontend/src/App.jsx - App navigation → Profile settings: renders
frontend/src/App.jsx - App navigation → Social feed: renders
frontend/src/App.jsx - App navigation → API client: loads library and history
frontend/src/App.jsx - Sign-in view → API client: requests auth
frontend/src/components/AuthPage.jsx - Workout logging → API client: requests data
frontend/src/api/client.js - Workout history → API client: requests data
frontend/src/components/History.jsx - Exercise analytics → API client: requests data
frontend/src/components/ExerciseAnalytics.jsx - Workout templates → API client: requests data
frontend/src/components/Templates.jsx - Nutrition tracking → API client: requests data
frontend/src/components/Nutrition.jsx - Nutrition tracking → Food presets: uses presets
frontend/src/components/Nutrition.jsx - Profile settings → API client: requests data
frontend/src/components/Profile.jsx - Social feed → API client: requests data
frontend/src/components/SocialFeed.jsx - API client → HTTP application: sends HTTP requests
frontend/src/api/client.js - HTTP application → Authentication: registers router
backend/main.py - HTTP application → Exercise library: registers router
backend/main.py - HTTP application → Workout records: registers router
backend/main.py - HTTP application → Account settings: registers router
backend/main.py - HTTP application → Template and progress: registers router
backend/main.py - HTTP application → Nutrition service: registers router
backend/main.py - HTTP application → Social features: registers router
backend/main.py - HTTP application → Relational database: creates tables
backend/main.py - HTTP application → Runtime configuration: loads settings
backend/main.py - HTTP application → Exercise library: seeds exercise data
backend/main.py - Authentication → Auth and DB dependencies: creates token
backend/routers/auth.py - Authentication → Request schemas: validates input
backend/routers/auth.py - Authentication → Domain models: reads and writes users
backend/routers/auth.py - Workout records → Auth and DB dependencies: requires user
backend/routers/workouts.py - Workout records → Request schemas: validates records
backend/routers/workouts.py - Workout records → Domain models: reads and writes
backend/routers/workouts.py - Template and progress → Auth and DB dependencies: requires user
backend/routers/templates.py - Template and progress → Request schemas: validates and shapes
backend/routers/templates.py - Template and progress → Domain models: reads and writes
backend/routers/templates.py - Nutrition service → Auth and DB dependencies: requires user
backend/routers/nutrition.py - Nutrition service → Request schemas: validates entries
backend/routers/nutrition.py - Nutrition service → Domain models: reads and writes
backend/routers/nutrition.py - Nutrition service → FatSecret API: queries foods
backend/routers/nutrition.py - Social features → Auth and DB dependencies: requires user
backend/routers/social.py - Social features → Request schemas: shapes responses
backend/routers/social.py - Social features → Domain models: reads and writes
backend/routers/social.py - Exercise library → Auth and DB dependencies: requires DB
backend/routers/library.py