$ show TandoorRecipes/recipes
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.
The LLM identified 6 files worth highlighting for reuse:
Unit conversion engine that models unit relationships as a graph and performs breadth-first search to find multi-step conversion paths, with cycle detection and fallback to base-unit tables. Demonstrates non-obvious algorithmic skill and is self-contained enough to be extracted into any project needing measurement conversion between arbitrary user-defined units.
Abstract base class for recipe import/export adapters. Centralizes cross-cutting concerns: zip size and traversal limits (zip-bomb protection), import logging, duplicate detection, keyword tree creation, and cache-based export. A clean example of the adapter pattern where 20+ concrete integrations implement a small interface (get_recipe_from_file, split_recipe_file, get_file_from_recipe) while inheriting robust, security-conscious scaffolding.
Singleton connector dispatch layer that bridges database-driven events to external services (e.g., Home Assistant) via a background thread + asyncio worker. Exposes a stable event API (on_shopping_list_entry_created/updated/deleted) decoupled from the Django ORM through dataclass DTOs. Demonstrates a reusable pattern for propagating application events to pluggable external integrations without blocking request handlers.
Bulk reference-data importer that syncs open datasets (e.g., USDA FDC-derived foods, units, categories, properties, supermarkets, conversions) into the tenant schema. Uses slug/fdc_id caches, conflict detection with _merge_if_conflicting, and per-item IntegrityError fallback to create-or-update idempotently. A practical template for any project needing repeatable, merge-safe ingestion of externally versioned dictionary data.
Self-contained parser for the Cooklang recipe file format, producing typed dataclasses for Recipe, Step, Ingredient, and Timer. Handles metadata, ingredient references with amounts, cookware, and timed steps with little coupling to the Tandoor ORM. Demonstrates a clean hand-written parsing pattern that could be lifted directly into any application needing Cooklang support.
Reusable Vue 3 composable that debounces user input before executing a search callback, cancels in-flight requests with AbortController, and binds the search state to URL query parameters with typed transformers. Framework-idiomatic, dependency-light, and directly portable to other Vue/TypeScript projects needing query-syncable debounced search.