How cjavsm/anima works
Project type and purpose
• This is a full-stack web application.
• Frontend (client/) is a React-based single-page application built with Vite.
• Backend (server/) is a Python FastAPI service exposing REST endpoints, using SQLAlchemy to talk to PostgreSQL and calling AWS Rekognition, Spotify API, and SMTP for email.
• database/ holds Docker Compose and init SQL for spinning up the Postgres database.
File structure
• Top‐level directories:
• client/ – all React code, styles, tests, config files (vite.config.js, package.json).
• server/ – FastAPI code organized into config, controllers, middlewares, models, routes, schemas, services, utils, tests, plus main.py.
• database/ – docker-compose.yml and init.sql.
• Patterns and layers:
• Frontend: “Services Layer” that makes HTTP calls, “Context API” for global state, “Pages/Components” under src/components.
• Backend: Routes → Controllers → Services → Models (ORM), with an Auth Middleware intercepting requests.
• Deployment/CI: GitHub Actions workflow for Python tests, Docker Compose for DB.
README for additional insights
“Cliente – Frontend,” “Servidor – Backend FastAPI,” and “Servicios Externos.”
• Shows how HTTP/REST, SQLAlchemy, boto3, spotipy, smtplib bind the components to external services.
Detail without overthinking
• Every logical component from the project tree (e.g., Auth middleware, individual service modules).
• Interaction path explicitly.
• Avoid overcrowding: group related controllers or models under a shared container if needed.