Add TandoorClient (app/tandoor.py) with full recipe creation, image upload, and duplicate detection via the Tandoor REST API. Settings page now has separate Mealie and Tandoor sections. Import page shows both send buttons based on which services are configured. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Recipe Importer
Docker container for importing recipes from Hungarian websites into Mealie and Tandoor Recipes.
Problem: Mealie's and Tandoor's built-in URL import cannot parse ingredients and instructions from Hungarian recipe sites like mindmegette.hu.
Solution: This container provides a web UI that scrapes Hungarian recipe pages with site-specific parsers, lets you review and edit the extracted data, then pushes it to Mealie and/or Tandoor via their REST APIs.
Architecture
┌──────────────────────────────────────────────────────┐
│ recipe-importer container (:8000) │
│ │
│ Flask + Gunicorn │
│ ├── /settings → Configure Mealie & Tandoor │
│ ├── /import → Paste URL, scrape, review │
│ ├── /scrape → AJAX: parse recipe HTML │
│ ├── /send → AJAX: push to Mealie API │
│ ├── /send-tandoor → AJAX: push to Tandoor API │
│ └── /health → Health check │
│ │
│ Modules: │
│ ├── app/config.py → JSON config persistence │
│ ├── app/scraper.py → Site-specific parsers │
│ ├── app/mealie.py → Mealie REST API client │
│ └── app/tandoor.py → Tandoor REST API client │
└───────────────────┬──────────────┬───────────────────┘
│ HTTP │ HTTP
▼ ▼
┌──────────────┐ ┌───────────────┐
│ Mealie │ │ Tandoor │
│ POST /api/.. │ │ POST /api/.. │
│ PUT /api/.. │ │ PUT /api/.. │
└──────────────┘ └───────────────┘
Supported Sites
| Site | Ingredients | Instructions | Image |
|---|---|---|---|
| mindmegette.hu | Yes | Yes | Yes |
| Other sites | Fallback (schema.org JSON-LD) | Fallback (schema.org JSON-LD) | Yes (og:image) |
Mindmegette.hu Parser
Extracts data from the Angular-rendered HTML:
- Title:
og:titlemeta tag, with| Mindmegette.husuffix stripped - Description:
og:descriptionmeta tag - Image:
og:imagemeta tag - Ingredients:
div.ingredients→div.ingredients-metarows, each containing<strong>(qty),<span>(unit),<a class="ingredients-link">(food),<small>(extra) - Ingredient groups: Multiple
div.ingredientscontainers; group title via<strong class="ingredients-group"> - Instructions:
mindmegette-wysiwyg-box→ol > lielements
Generic Fallback Parser
For unsupported sites, attempts extraction via:
- Schema.org JSON-LD
@type: Recipeblocks (recipeIngredient,recipeInstructions) - OpenGraph meta tags for title, description, image
Adding a New Site Parser
- Create a parser function in
app/scraper.pywith the@_register("hostname")decorator - The function receives
(soup: BeautifulSoup, url: str)and returns the standard recipe dict - The hostname substring is matched against the URL — first match wins, unmatched URLs use the generic fallback
Mealie API Integration
The importer uses the Mealie REST API:
- POST
/api/recipes— create a stub recipe (returns slug) - PATCH
/api/recipes/{slug}— populate structured ingredients (with unit/food IDs), instructions, description, orgURL - PUT
/api/recipes/{slug}/image— upload the recipe image
Structured ingredients: The client resolves unit and food names to Mealie database IDs. Missing units/foods are created automatically via the API. Ingredient groups are supported via the title field on the first ingredient of each group.
Authentication uses a long-lived API token (Bearer header), created in Mealie at Profile → API Tokens.
Tandoor API Integration
The importer uses the Tandoor REST API:
- POST
/api/recipe/— create the full recipe in one call (name, description, source_url, steps with nested ingredients) - PUT
/api/recipe/{id}/image/— upload the recipe image
Step-based ingredients: Tandoor nests ingredients inside steps. All ingredients are attached to the first step. Units and foods are auto-created by name (no separate resolution needed). Ingredient groups use is_header: true on a header entry.
Duplicate detection: Before import, searches Tandoor by title and checks the source_url field to detect already-imported recipes.
Authentication uses an API token (Bearer header), created in Tandoor at Settings → API Browser → Auth Token.
Configuration
All settings are persisted to /data/config.json (mounted as a Docker volume).
| Setting | Description |
|---|---|
mealie_url |
Full URL to Mealie instance (e.g. https://mealie.example.com) |
mealie_api_key |
Mealie API token |
tandoor_url |
Full URL to Tandoor instance (e.g. https://recipes.example.com) |
tandoor_api_key |
Tandoor API token |
Deployment
Docker Compose
services:
recipe-importer:
image: gitea.dooplex.hu/admin/recipe-importer:0.1.9
container_name: recipe-importer
restart: unless-stopped
ports:
- "8011:8000"
volumes:
- recipe-data:/data
environment:
- SECRET_KEY=change-me-in-production
- MEALIE_INTERNAL_URL=http://mealie:9000
- TANDOOR_INTERNAL_URL=http://tandoor:8080
volumes:
recipe-data:
Environment Variables
| Variable | Default | Description |
|---|---|---|
SECRET_KEY |
recipe-importer-dev-key |
Flask session secret |
DATA_DIR |
/data |
Persistent storage path |
VERSION |
dev |
Shown in the UI navbar |
MEALIE_INTERNAL_URL |
(empty) | Docker-internal Mealie URL (e.g. http://mealie:9000) to avoid Cloudflare hairpin |
TANDOOR_INTERNAL_URL |
(empty) | Docker-internal Tandoor URL (e.g. http://tandoor:8080) to avoid Cloudflare hairpin |
Building
On the build server (kisfenyo@192.168.0.180):
cd ~/build/recipe-importer
./build.sh X.X.X --push
Web UI
The UI is in Hungarian and uses a dark theme. The workflow is:
- Settings (
/settings) — Configure Mealie and/or Tandoor connection (URL + API key), test each connection - Import (
/import) — Paste a recipe URL, click "Beolvasás" (Scrape) - Review — Edit structured ingredients (4-column: quantity, unit, food, note), add/remove ingredient groups, edit instructions
- Send — Click "Importálás Mealie-be" and/or "Importálás Tandoor-ba" to push to your configured services
Tech Stack
- Runtime: Python 3.12 (slim)
- Web framework: Flask 3.1 + Gunicorn
- HTML parsing: BeautifulSoup 4 + lxml
- HTTP client: requests
- Container: ~60 MB image