How steven030397/tdp-project-drive2 works
Project type and purpose
• This is a full-stack carpool matching platform.
• Purpose: collect user routes and profiles, run matching algorithms in the background, store and serve data, and present UI with embedded data visualizations.
File structure
• Top-level folders:
• Frontend – Flask app serving HTML templates and static assets (CSS, JS, images, Tableau embeds)
• Backend – Node.js/Express service exposing data APIs; contains docker-compose, mock-data generators, and tests
• API-Algo – Python/Flask microservice wrapping matching logic and exposing it via HTTP endpoints
• Algorithms – standalone Jupyter notebooks and scripts used offline to prototype/tune matching logic (not part of online service)
• Config/deployment files:
• Backend/compose.yml – orchestrates containers for Frontend, Backend, API-Algo, and MySQL
• requirements.txt & package.json (implied) – declare Python and Node.js dependencies
README for additional insights
• Confirms Python 3.11 for Flask services, Node.js for data API, periodic background execution of matching algorithm.
• Database: MySQL hosted on db4free.net. Credentials provided.
• Frontend uses Flask’s routing to serve pages and embed Tableau Cloud dashboards.