How p4bl1t0ck/urbanex works
Urbanex is a small web application centered on email-and-password login, account lockout, JWT issuance, and a session-gated dashboard. The browser login calls the shared API client; Django routes the request to the login view, which validates input, checks and updates the user, and returns tokens. The dashboard checks the stored access token and supports logout. The README describes the Django/Next.js setup but documents no other product capabilities. Source excerpts do not show all model or database behavior, so those links are limited to explicit ORM and settings evidence.
Main entry points: views.py Login handler · page.tsx Login page · api.ts API client · urls.py API routing
Components 11
Web client
- Login page
frontend/app/(auth)/login/page.tsx - API client
frontend/lib/api.ts - Dashboard
frontend/app/dashboard/page.tsx
Django API
- API routing
backend/config/urls.py - Auth routes
backend/apps/users/urls.py - Login handler
backend/apps/users/views.py - Login validation
backend/apps/users/serializers.py - Backend settings
backend/config/settings.py
Identity data
- User account model
backend/apps/users/models.py - SQLite database
backend/db.sqlite3
Other components
- User
Connections 10
- User → Login page: submits credentials
frontend/app/(auth)/login/page.tsx - Login page → API client: calls
frontend/app/(auth)/login/page.tsx - API client → API routing: posts login request
frontend/lib/api.ts - API routing → Auth routes: includes routes
backend/config/urls.py - Auth routes → Login handler: routes login
backend/apps/users/urls.py - Login handler → Login validation: validates with
backend/apps/users/views.py - Login handler → User account model: queries and updates
backend/apps/users/views.py - Backend settings → SQLite database: configures database
backend/config/settings.py - Login handler → Dashboard: returns tokens; client navigates
- User → Dashboard: uses session
frontend/app/dashboard/page.tsx