How takujoye14/fit-company works
Project type and purpose
• This is a Python-based monolithic REST API (“fit monolith”) providing endpoints for an AI fitness coach.
• It exposes routes for authentication, user management, fitness data retrieval, and profile management.
• Docker is used to launch the database via docker‐compose; testing is done with pytest; “Bruno” collections exercise the API.
File structure
• Top‐level artifacts:
• Dockerfile, docker-compose.yml – containerization
• main.py – entry point / Uvicorn server launcher
• pyproject.toml – Python dependencies
• src/fit – application code
• tests – pytest suite
• bruno/ – API request collection
• Inside src/fit:
• app.py – FastAPI (or similar) app instantiation
• database.py & db_init_scripts – DB connection & initialization scripts
• models_db.py & models_dto.py – ORM/DB schemas and data‐transfer objects
• routes/ – HTTP routers (auth, fitness, profile, user)
• services/ – business logic (auth_service, user_service, fitness_service, fitness_data_init, fitness_coach_service)
README for additional insights
• Confirms startup steps: docker compose up for DB, uv sync + ./main.py to run server.
• Encourages use of Bruno collection for API exploration.
• No built‐in frontend; it’s an API service only.
Essential elements
• Labels for each layer/component
• Deployment context: Docker host, docker-compose network