How alexander-tibanta23/polimusic works
Project type and purpose
• This is a full-stack web application for browsing, playing and organizing music tracks, with user authentication, favorites, listening history and a chat feature.
• The “fronted” folder holds an Angular SPA; the “backend” folder holds a Flask REST API, static MP3 assets and the built Angular app; the “database” folder holds init and seed scripts; docker-compose wires the services together.
File structure
• Top-level folders:
• fronted: Angular 14+ application (modules: auth, home, tracks, favorites, history; shared UI components)
• backend: Python Flask app (routes/controllers, service layer, model/ORM layer), static assets (MP3s and built Angular distribution), config and utility helpers
• database: shell and SQL scripts to initialize and seed a relational database
• docker-compose.yml: definitions for the backend service, the database service (e.g. PostgreSQL/MySQL) and any supporting containers
• The Flask app follows a layered MVC-style pattern:
• app/routes ↔ app/services ↔ app/models/database
• app/utils holds common response formatting and validators
• The frontend uses a modular Angular structure with feature modules, shared components, core models and a tracks.json used for offline data or testing.
Review README for architectural hints
• Although the README is placeholder, the file tree and folder names make the stack and responsibilities explicit.
Detail
• Drill down to subcomponents as needed (i.e., show that the Angular Tracks Module depends on a TracksService that issues HTTP GET /api/music/…)
• Environment variables or secrets managed by Docker-Compose