How freedy-fr/ci-p5-magnaplate works
Project Type and Purpose
• This is a monolithic full-stack e-commerce web application built with Django (Python) that lets customers browse and purchase magnetic posters.
• Major concerns: user-facing storefront (products, cart, checkout, profiles, favorites), admin/Site-Management, payment integration (Stripe), file storage (AWS S3), and relational data (PostgreSQL).
File Structure Highlights
• Top-level Django project: manage.py, magnaplate/ (settings, URLs, WSGI/ASGI).
• Apps by feature: cart, checkout, favorites, footer, home, products, profiles (+ custom_storages, templates for allauth).
• Static & media: local static/, staticfiles/ (collected), media/ (user uploads).
• Dev/deploy: .devcontainer/, docker-compose.yml, Procfile, gitpod.yml.
• Configuration: requirements.txt, package-lock.json, robots.txt, sitemap.xml.
Key Architectural Patterns
• MVC: Django views ↔ templates (UI) ↔ models (DB).
• Modular app-per-feature for separation of concerns.
• Third-party integrations:
• Stripe for payments/webhooks
• AWS S3 via django-storages for static/media
• ElephantSQL (PostgreSQL) via dj-database-url
• Allauth for authentication
• Easy Thumbnails, Crispy Forms, Widget Tweaks
Main Components
A. Clients (Web Browser / Mobile)
B. CDN / AWS S3
• StaticAssets (CSS/JS/images)
• MediaAssets (product images, user uploads)
C. Heroku Router & Dyno
• Gunicorn WSGI server hosting Django app
• Docker container (optional) via .devcontainer
D. Django Application
• URLs & Views (cart, checkout, products, profiles, admin)
• Templates (Django + allauth)
• Business Logic (signals, context_processors, management commands)
• Custom Storage backends (custom_storages.py)
E. Database Layer
• PostgreSQL (ElephantSQL)
• Models: Order, OrderLineItem, Product, Category, Collection, Creator, UserProfile, Favorites, Newsletter, Carousel, SupportInquiry
F. External Services
• Stripe API & Webhooks
• Email (SMTP via Django)
• Google Fonts / FontAwesome / fslightbox (CDN)
Relationships & Data Flow
1. Client → DNS → Heroku Router → Gunicorn
2. Gunicorn → Django URL dispatcher → appropriate app-view
3. View ↔ Database queries (PostgreSQL)
4. View ↔ AWS S3 for file/media operations
5. Checkout View → Stripe API for PaymentIntent → Stripe Webhook → webhook_handler updates Order
6. Email notifications sent via SMTP or managed via Django’s EmailBackend
7. Admin users ↔ Django Admin → Database