Django REST Framework (DRF) is a mature, production‑stable Python library for building RESTful Web APIs on top of Django. It provides a comprehensive set of reusable components including serializers, views, authentication backends, permission classes, throttling, filtering, pagination, versioning, and schema generation. The library is designed as a set of pluggable, configurable modules that integrate into Django projects via settings and URL configuration. Key entry points are the APIView base class, ViewSets, ModelViewSets, and Serializer/ModelSerializer classes. Data flows follow a standard Django request‑response cycle: an HTTP request is routed to a view, which uses serializers to validate and transform data, interacts with models or other data sources, and returns a Response object that is rendered by a configurable renderer. External dependencies include Django (5.2–6.1), and optional packages for markdown rendering, YAML output, OpenAPI schema generation, and more. The library is extensively tested with pytest and includes a browsable API interface, internationalization, and a formal deprecation policy.
Tandoor is a self-hosted, multi-tenant recipe management web application. The system is a monolithic Django application (cookbook app) exposing a Django REST Framework API, paired with a Vue 3 + Vuetify single-page frontend that consumes an auto-generated TypeScript OpenAPI client. Core production domains, verified in code, are: structured recipes (steps, ingredients, scaling), a tree-based hierarchical food database with nutritional properties and USDA FDC IDs, meal planning with iCal export, shopping lists with supermarket categories and offline sync queues, inventory/pantry booking, cookbooks, share links, and view/cook logging. Tenancy is enforced through Space/Household/UserSpace models with django-scopes middleware and granular guest/user/admin permission classes rather than through database row-level security. The largest subsystem is recipe import/export: an abstract Integration base class with 20+ adapters for other recipe managers (Paprika, Mealie, Cooklang, Gourmet, ChefTap, etc.), URL scraping via recipe-scrapers/microdata/pytubefix, cloud storage sync providers (Dropbox, Nextcloud, WebDAV, local), a bulk open-data importer for USDA-derived reference foods/units/conversions, and an embedded PDF.js viewer for external recipe files. A connector/event layer dispatches async updates to external services such as Home Assistant, a Telegram bot webhook writes shopping list entries, and recent AI features (litellm-based, per-space credit tracked) handle image/PDF recipe import, step sorting, and nutrition extraction. Background work is done via threads rather than a task queue. Craftsmanship is above average: clean abstract patterns (Integration, Provider, Connector ABCs), chainable queryset managers, mixin-based permission/merge/tree logic, a strong permission-matrix test suite, and genuinely reusable helper algorithms (BFS unit conversion, ingredient parsing, Cooklang parsing). However, the codebase carries notable debt: 240+ migrations with heavy schema churn, a ~3000-line monolithic api.py view file, committed auto-generated OpenAPI client code that can drift, vendored PDF.js binaries, some tests that suppress tenant scoping via scopes_disabled, and copy-paste duplication inside the open-data importer. Overall it is a well-maintained, actively developed application with solid architecture for its scale.
django-init is a cookiecutter template for generating Django-based REST API projects. It provides a comprehensive starting point with Django 4.1, Python 3.9, Poetry dependency management, Django REST Framework, and optional features like Celery, GraphQL, ASGI, Docker, and various deployment configurations. The template generates projects with custom user models, JWT authentication, proper API versioning, and testing setup. What distinguishes this template is the quality of its reusable components in the base/ directory, particularly the custom DRF mixins for multiple serializers and per-action permissions, specialized routers for singleton resources, and thoughtful exception handling and response classes that demonstrate deep understanding of Django REST Framework's architecture.
MediaCMS is a production-grade, self-hosted video and media content management platform built as a Django monolith with a React frontend. In production it ingests video, audio, image, and PDF uploads via a chunked Fine Uploader flow, transcodes video through FFmpeg into multiple MP4/HLS renditions matched by configurable encoding profiles, streams them through a customized video.js player, and supports subtitles (manual upload and Whisper transcription), chapter markers, video trimming/editing, playlists, comments with mention notifications, likes, reports, and PostgreSQL full-text search. It ships a REST API under /api/v1/, an editor/manager admin UI, RSS feeds with Yahoo Media RSS extensions, and a small Click-based CLI. The backend is organized into Django apps (files, users, actions, rbac, lti, saml_auth, identity_providers, migrationservice, uploader) with DRF serializers/views, Celery workers for encoding and notifications, Redis as broker, and Nginx serving protected media through an auth_request subrequest. A significant portion is education/LMS-focused: an LTI 1.3 tool provider with deep linking, SAML authentication, RBAC groups mapped to categories, Moodle filter and TinyMCE plugins, and a migration service that imports media, captions, and users from Kaltura, Panopto, and YouTube with quiet-hours scheduling and encrypted credentials. This gives the repository a mild data-pipeline flavor through the migration service, but its dominant character is a full web application. Engineering quality is strong for an open-source Django project: extensive pytest coverage across API, permissions, LTI, SAML, RBAC, migration providers, and pipeline tasks; a large Jest suite for frontend components, hooks, and stores; semantic-release and pre-commit CI; and a clean provider abstraction for migration sources. Weaknesses include legacy webpack-built minified bundles checked into static/, a mix of JSX and TSX across the frontend, duplicated iOS player code between the video-editor and chapters-editor tools, several TODO/FIXME markers, and version-sensitive external dependencies (yt-dlp, Moodle, LTI). Overall it is an actively maintained codebase with several genuinely reusable components, though it carries moderate legacy debt in its frontend tooling.
GreedyBear is a threat intelligence platform that consumes honeypot logs from T-Pot clusters (Cowrie, Heralding, Tanner, etc.), extracts Indicators of Compromise (IOCs), enriches them with external threat feeds (ThreatFox, AbuseIPDB, FireHol, Spamhaus, MalwareBazaar), and applies machine learning scoring (Random Forest) to predict recurrence probability and expected interactions. The system exposes public and authenticated APIs in multiple formats (JSON, NDJSON, CSV, TXT, STIX 2.1) for threat researchers and supports event ingestion from external sensors. The backend is built with Django/DRF, PostgreSQL, and Elasticsearch, orchestrated via Django-Q cronjobs for scheduled extraction, enrichment, and cleanup. A React SPA frontend provides a customizable dashboard with attack maps, trending attackers, and feed browsing. The architecture uses repository, strategy, and factory patterns, with a clean separation between extraction pipelines, scoring, and API layers. While primarily an application, it has strong data engineering components—ETL pipelines, ML scoring, clustering (MinHash LSH for command sequences), and data enrichment—making it a hybrid that leans application.
This repository is an AI-driven story-to-video production platform. It is a full-stack Django 3.2 backend with Vue 2 frontend, Celery task queue, Redis pub/sub, and Docker deployment. The system ingests user story ideas and orchestrates a multi-stage pipeline: rewrite → storyboard → image generation (text2image/image2video) → camera movement → video generation → Jianying (剪映) draft export. All AI capabilities are consumed via external APIs (OpenAI, ComfyUI, Volcano Engine, etc.) through a pluggable AI client abstraction layer. Key entry points include RESTful APIs (DRF), SSE streaming for real-time progress, MCP (Model Context Protocol) JSON-RPC endpoints for agent integration, and a Vue-based canvas UI for visual workflow editing. The architecture follows a modular Django app pattern with clear separation: core infrastructure (pipeline orchestration, AI clients, Redis streaming), domain apps (projects, prompts, models, workflows, content, agent, MCP), and a frontend SPA. External dependencies include Redis, Celery, MySQL/PostgreSQL, external AI vendor APIs, and optional Jianying draft generation. The codebase demonstrates strong engineering practices with reusable patterns for AI client abstraction, Redis pub/sub streaming, MCP tool registration, and pipeline stage processors, but has notable technical debt: Django 3.2 (EOL), mixed async/gevent, Vue 2 (EOL), and some closed-source compiled components.
HydroShare is a Django-based web application for sharing, managing, and publishing hydrologic data and models. It provides a rich resource management system with support for various file types (NetCDF, GeoTIFF, timeseries, etc.), fine-grained access control (groups, communities, privileges), metadata extraction, and discovery via a Vue.js frontend. The system uses PostgreSQL, Redis, Celery, MinIO (S3-compatible storage), and MongoDB for indexing. It exposes REST APIs for programmatic access and includes background tasks for bag creation, metadata extraction, and DOI registration. While primarily an application, it incorporates data engineering patterns for scientific metadata handling and file type aggregation.
This repository is an educational Docker tutorial centered on a functional Django REST API application. The core implementation uses Docker Compose to orchestrate two services: a Django web container (DRF) and a PostgreSQL container, with explicit health checks, JSON-file logging limitations, named volumes, and user-defined networks. The Django API itself is a basic music CRUD service with endpoints under /api/musics, secured behind authentication, and housed in a straightforward project structure that demonstrates the typical pattern of a containerized Python microservice. Beyond the main tutorial, the repo provides stand-alone Docker Compose examples covering advanced patterns: YAML anchors to reduce configuration repetition, docker-compose override to batch operate multiple databases, environment variable substitution with .env files, profiles for selective service boot, and cAdvisor for container resource monitoring. Each subfolder includes a README and ready-to-run configuration, making the entire repository a one-stop teaching resource for Docker Compose patterns and best practices. The code is not intended as a production tool but rather as a self-contained, reproducible learning blueprint that shows how to build and manage containerized stacks with modern features. While the application layer is deliberately simple, the Docker-compose layer embodies several good practices around health and logging, and the advanced usage of YAML anchors and overrides exemplifies high-quality configuration craftsmanship that is directly reusable in other projects.
This repository is a Russian-language translation mirror of the official Django REST Framework documentation. It does not contain any runnable application, API, or library code; the core content is a set of Markdown files mirroring the upstream DRF docs. The repo's functional value lies in its automation scripts and CI workflows that periodically check the upstream repository for changes, compare file hashes, and open pull requests to flag new or modified content that needs translation. The automation pipeline (`monitor_repository.py`, `commit_changes.py`) is a self-contained, reusable pattern for keeping translated documentation in sync with a source repository. The workflows (`check_source_for_changes.yml`, `check_all_temp_data_cleared.yml`) demonstrate practical GitHub Actions usage for doc-sync automation. The repository is not a software application in the traditional sense but a hybrid documentation project with a small but well-crafted automation component.
Estela is an open-source web scraping orchestration platform (analogous to Scrapy Cloud) for deploying, scheduling, and monitoring Scrapy-based spider projects on Kubernetes. It consists of a Django REST API backend with Celery for async task management, a React/TypeScript frontend with Ant Design, and a Kafka-based queue consumer for streaming scraped data into MongoDB. Core workflows include project management, spider deployment (Docker image build via Kaniko), job execution with configurable resource tiers, cron scheduling, data persistence settings, and a metering subsystem for usage tracking. The system relies on external dependencies such as Kubernetes, Kafka, MySQL, MongoDB, Redis, and object storage (MinIO/S3). The frontend provides interactive charts, a tour overlay for onboarding, and notification management. While functional and extensible, the codebase shows signs of age (outdated Django/Celery versions, class-heavy React components, duplicate logic in cron expression handling) and has incomplete test coverage.
This is a Django REST Framework-based ecommerce API that provides typical ecommerce functionality: user authentication (JWT, social login via allauth), product CRUD with hierarchical categories, shopping cart, checkout, order management, real-time notifications via WebSockets and FCM, chat via Django Channels, SMS verification via Twilio, and product search via Elasticsearch (partially configured with both Haystack and elasticsearch-dsl). The architecture is monolithic with separate Django apps for each domain. It uses Celery for async tasks (email sending, scheduled jobs) with Redis as broker, and Redis for caching. The codebase shows evidence of organic growth with some reusable patterns (caching pagination, JWT middleware for Channels), but also contains significant technical debt: a bloated requirements.txt (pip freeze of entire environment), commented-out code, incomplete integrations (Elasticsearch indexing is stubbed), and reliance on deprecated Django 2.2 APIs (ugettext_lazy). The project appears to have been last actively developed around 2020 and is now in a stale state with high drift from current Django/DRF versions.
This repository is a curated list (awesome list) of Django packages, projects, and resources. It contains no application code, no data pipelines, and no executable software. The sole functional content is a README.md file that organizes hundreds of external links into categories such as admin interfaces, authentication, REST APIs, CMS, e-commerce, etc. The repository includes CI configurations (Travis, GitLab CI) that validate links in the README, and a requirements.txt file for the Markdown library used in link checking. It is not a software application or data research project; it is a documentation/curation resource. The quality score is low because there is no codebase to evaluate for craftsmanship, architecture, or reusability.