How mikebgrep/forkapi works
Main Components
a) Client Layer:
• External Web Clients (fork.recipes frontend)
• Admin Panel (Django Admin with Jazzmin)
• Third-party API Consumers
b) Nginx Layer:
• Reverse Proxy
• SSL Termination (optional configuration)
• Static/Media File Serving
c) Application Layer:
• Django Application Server (uWSGI)
• Two main Django Apps:
• Authentication Module
• Recipe Module
• OpenAI Integration (for recipe scraping)
d) Data Layer:
• SQLite Database
• Media Storage (for recipe media files)
Component Relationships
• Client requests → Nginx → Django Application
• Django Application ↔ SQLite Database
• Django Application ↔ Media Storage
• Recipe Module ↔ OpenAI API
• Authentication Module ↔ Token Management
Specific Implementation Details
• Blue rectangles: External interfaces (Nginx, Client applications)
• Green rectangles: Core application components (Django apps)
• Purple clouds: External services (OpenAI)
Authentication Flow
Two authentication methods:
• Header Authentication (for read operations)
• Token Authentication (for create/update operations)
Key Technical Elements
Important components:
• uWSGI application server
• Django REST Framework endpoints
• Admin Panel with Jazzmin interface
• Docker containerization boundary
Additional Notes
• Request flow directions
• Authentication boundaries
• Container boundaries
• Environment configurations