How lencodigitexer/photo-portfolio-django works
Project Type & Purpose
• A full-stack Django web application (“photo_portfolio”) for managing and displaying user photos and avatars.
Main Components
a. Client (Web Browser/REST Client)
b. Django App Server
• URL Router (photo_portfolio/urls.py + photos/urls.py)
• Views & REST API (photos/views.py + DRF serializers)
• Models & Business Logic (photos/models.py + signals.py + permissions.py)
c. Database (SQLite: db.sqlite3)
d. Media Storage (photo uploads & avatars in photo_portfolio/media)
e. Admin Interface (photos/admin.py)
Component Interactions
• Client → HTTP(S) → Django URL Router
• Router dispatches to Views/REST endpoints
• Views use Serializers → translate JSON ↔ Models
• Models ↔ ORM → SQLite
• File uploads/downloads → Media Storage
• Signals trigger side-effects (e.g., thumbnail generation)
• Admin UI ↔ ORM ↔ Database
Architectural Patterns & Tech
• MTV (Model-Template-View) / REST API (Django REST Framework)
• Modular “photos” app
• Migrations for schema evolution
• Signal-based hooks for post-save logic