How zeck7one/mycar works
This is a Flask vehicle-records and community web app, with user accounts, profile/car settings, messaging, and an administrator view. The principal workflow is a user entering the app, managing vehicle records, and using community features; Supabase is the documented persistence service. The sampled source shows record queries, profile updates, admin checks, and community-feed handling. Other feature routes are visible only indirectly through the file tree and partial excerpts, so their internal calls are not inferred.
Main entry points: app.py Flask app · supabase_schema.sql Supabase data · templates Web pages
Components 13
Web application
- Flask app
app.py - Accounts and login
app.py - Web pages
templates - Profile
app.py
Vehicle records
- Record management
app.py - Car settings
app.py
Community
- Community feed
app.py - Community posting
app.py
Messaging and administration
- User messages
app.py - Admin messages
app.py - Admin access checks
app.py
Persistence
- Supabase data
supabase_schema.sql
Other components
- User
Connections 16
- User → Flask app: uses
README.md - Flask app → Accounts and login: dispatches
app.py - Flask app → Record management: dispatches
app.py - Flask app → Car settings: dispatches
app.py - Flask app → Profile: dispatches
app.py - Flask app → Community feed: dispatches
app.py - Flask app → Community posting: dispatches
app.py - Flask app → User messages: dispatches
app.py - Flask app → Admin messages: dispatches
app.py - Admin messages → Admin access checks: checks access
app.py - Record management → Supabase data: queries records
app.py - Car settings → Supabase data: reads and updates
app.py - Profile → Supabase data: updates profile
app.py - Admin access checks → Supabase data: checks role
app.py - Community feed → Supabase data: reads and updates
app.py - Flask app → Web pages: renders pages
app.py