How revathybalaji06-commits/smart-parking works
This is a smart-parking reservation design, but the repository currently contains only the PostgreSQL schema and seed data. The documented workflow is: a driver provides a vehicle class, the backend finds the smallest available slot that fits, records the reservation, and returns a slot-specific route. The frontend, backend logic, and sensing are planned rather than implemented here; those relationships reflect the README, not inspected source code.
Main entry points: schema.sql Parking database · seed.sql Initial slot data
Components 9
Parking application
- Driver frontend
- API and matching
- Size-aware slot match
- Slot routing
- Live availability
Parking data
- Parking database
schema.sql - Initial slot data
seed.sql
Other components
- Driver
- Sensors
Connections 11
- Driver → Driver frontend: submits class
README.md - Driver frontend → API and matching: sends requests
README.md - API and matching → Driver frontend: returns slot
README.md - Driver frontend → Driver: shows route
README.md - Sensors → API and matching: reports events
README.md - API and matching → Size-aware slot match: matches vehicle
README.md - API and matching → Parking database: reads and writes
README.md - API and matching → Slot routing: routes assigned slot
README.md - API and matching → Live availability: updates counts
README.md - Size-aware slot match → Parking database: selects fitting slot
README.md - Initial slot data → Parking database: creates slots
README.md