How jeevanba273/vehicle-parking-system works
Project Type and Purpose
• This is a full-stack Vehicle Parking System.
• Frontend: Vue.js 3 SPA with TypeScript, Pinia, Vue Router, Bootstrap, Chart.js.
• Backend: Flask REST API with SQLAlchemy, SQLite, Flask-Security (auth), optional Redis cache, Celery tasks.
• Purpose: Allow users to sign up/login, book/release parking spots, view history; allow admins to manage lots, users, and view analytics in real time.
File Structure
• Top level:
• /frontend: source of the Vue.js SPA
• /backend: Flask API server
• Deployment guides and configs (Netlify, Railway, Dockerfile, Procfile)
• Frontend details:
• src/components, views, router, stores indicate an SPA with component-based UI, state management via Pinia, and client-side routing
• config/api.ts defines the base API URL
• Backend details:
• Single entry app.py exposing /api/* routes (auth, parking-lots, bookings, analytics)
• SQLAlchemy models and Flask-Security for RBAC
• Celery integration for background jobs (e.g., scheduled occupancy metrics)
• Deployment artifacts:
• frontend/netlify.toml, _redirects for SPA routing on Netlify
• backend/railway.json, Procfile, Dockerfile for containerized/Railway deploy
README for Additional Insights
• API endpoints: clear REST routes for auth, parking lots, spots, bookings, analytics
• Tech stack reinforces components: Vue UI, Flask API, SQLite DB, Redis, Celery
• Real-time updates likely via polling or WebSocket/local refresh (not explicitly in code, but implied by “Real-time Updates”)
Detail
• User roles (Admin vs. User) and their UI entry points (AdminDashboard.vue vs. UserDashboard.vue)
• Real-time/update mechanism (polling or WebSocket if present)
• Deployment specifics: how CI/CD pushes changes to Netlify and Railway