How viralone/smartcommute works
Project type and purpose
• From the file tree and README, this is a single-page, static web application (“Bus LiveMap”) whose sole job is to display real-time bus locations on a map in the user’s browser.
• No custom backend code is present; instead it fetches data from an external “Bus API” and uses Leaflet (map rendering) and Bulma (CSS).
File structure
• Top-level files:
• Dockerfile & docker-compose.yaml – containerize the static site (likely serving via nginx).
• index.html – entry point.
• css/style.css – custom styling.
• js/functions.js – all application logic (map setup, API calls, UI interactions).
• .github/workflows/deploy_changes.yaml – CI/CD pipeline.
• No “src/backend” or database directories, confirming it’s purely a front-end deliverable.
README for additional insights
• Describes Leaflet & Bulma usage.
• Explains the app fetches bus locations from an external Bus API.
• Documents Docker build & run steps.
• Lists map features (follow bus, show stops, recent buses).
Detail without over-splitting
• You don’t need microservices or deep infrastructure layers here.
• Three runtime actors (Browser, Static Server, External APIs) plus CI/CD.
• This level of separation fully conveys how data flows and where responsibilities lie.