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.
PriceBuddy is a self-hosted price tracking application built with Laravel and Filament. It monitors product prices across multiple retailers, sends notifications for price changes and stock availability, and provides insights like deal scores and seasonality analysis. The system features a web interface, API, and CLI for interaction, with background jobs handling periodic price checks. AI-assisted scraping is available for difficult sites. The architecture follows Laravel conventions with Eloquent ORM, event-driven notifications, and a modular service layer. Docker deployment simplifies setup with separate containers for app, database, and scraper services.
OpenCart is a free and open-source e-commerce platform written in PHP. It provides a complete online store solution with both a storefront (catalog) and an administrative backend. The architecture follows a custom MVC framework with a route-based dispatch system, event hooks, and an extension system for payments, shipping, modules, and themes. The frontend uses a mix of jQuery (admin) and a custom WebComponent framework (catalog) with a custom template language called Curlytag. The system supports multi-store, multi-language, and multi-currency out of the box, with background task processing for cache generation and email delivery. In production, OpenCart handles product catalog management, shopping cart and checkout flows, customer accounts, order processing, payment integration, shipping calculations, tax handling, and reporting. It includes CMS capabilities (articles, blogs, comments), GDPR compliance tools, and SEO-friendly URL rewriting. The admin panel provides full control over store settings, localization, user permissions, and extension management. Key entry points include the storefront index.php (catalog), admin/index.php (admin panel), and system/framework.php (application bootstrap). External dependencies include a database (MySQL/PostgreSQL), optional caching (Redis/Memcached), and third-party libraries for email, template rendering (Twig), and code editing (CodeMirror). The system is designed to be extensible through a plugin architecture that allows adding new payment gateways, shipping methods, and frontend modules.