# Recipe Match demo Run the Recipes migration, then open **Recipes → Try Recipe Match** (`/recipes/match/`). The demo uses existing recipes. It does not change the normal recipe library, inventory, or Food Diary. The demo account is selected by `TASKNEST_RECIPE_MATCH_DEMO_USERNAME` (default: `demo`). Only that account's **published** recipes are shown to other users in this view. Each user also sees their own recipes. Other users' recipes remain private. The normal recipe detail and photo routes retain their owner checks; published demo photos use a separate match-only route. Seed selections from up to ten published recipes owned by the demo account: ```sh python manage.py seed_recipe_match ``` If the demo account has no published recipes, an operator can explicitly select a participant's existing recipes for the demo account. Those recipes appear only to their owner; this does not copy or expose them to other users: ```sh python manage.py seed_recipe_match --source-username PARTICIPANT --reset-demo ``` For another run, reset the participant's selections, then visit Recipe Match again: ```sh python manage.py seed_recipe_match --reset-user PARTICIPANT ``` `--reset-demo` clears and rebuilds only the demo account's selections. The command never creates or duplicates recipes. Selection is idempotent, and skipped cards reappear on a fresh visit. No matching presence or messaging is involved.