How pineapple-epita/fit-company works
Project type and purpose
• From the README (“The fit monolith is a blazing fast, cutting edge AI fitness coach”) plus the file tree, this is a hybrid Python fitness-coach application in transition from a monolith toward microservices. It provides authentication, user management, fitness coaching (WODs), profiles, etc., and can be exercised via the Bruno API-testing collection.
File structure
• Top level
• Dockerfile, docker-compose.yml, nginx.conf → containerized deployment with an API gateway (NGINX) and services
• main.py → monolithic application entrypoint (“fit” monolith)
• src/fit/ → current monolith (Flask blueprints: auth, fitness, profile, user; models; database init)
• src/coach_microservice/ & src/user_microservice/ → two standalone microservices (each with its own Dockerfile, app.py, models, services)
• docs/, adr/ → documentation and architectural decision records
• Tests folder contains unit and load tests against the APIs.
• bruno/ holds API requests for the Bruno client.
README for additional insights
• Single command (“docker compose up -d”) to start the database
• “uv sync” / “./main.py” to run the monolith
• Encourages using Bruno for API exploration
• Tests are run via pytest
Essential details
• Environment files or config mounts if relevant (e.g., volumes in docker-compose)
• Ports (e.g., 80 on NGINX, 8000 on monolith, 8001/8002 on services)