Recipe catalog¶

Rezeptor lists applications as recipes. The catalog distinguishes origin and trust — not every source is equivalent.

Official recipes (bundled)¶

Shipped in the repository under recipes/<id>/, indexed in recipes/catalog.json (trust: official).

Examples: Photoshop, Premiere Pro, WISO Steuer, House of Ashes, ZA4 trainer.

These recipes ship with Rezeptor and are guarded by CI (recipe-lint, manifest checks).

Community recipes¶

Custom or shared recipes live under recipes/community/<id>/.

Create one with:

./scripts/new-recipe.sh --community my-app "My App"

Community entries are not automatically vetted as official — author and content are your responsibility.

Recipe sync (official updates without app reinstall)¶

Packaged builds ship a read-only recipes/ tree. Rezeptor can still pull newer official recipes from the GitHub Release asset rezeptor-recipes-<version>.tar.gz (listed in SHA256SUMS).

Piece	Location
Overlay	`~/.local/share/rezeptor/recipes/` (wins over bundled same `id`)
Overlay manifest	`~/.local/share/rezeptor/manifest.overlay.json`
State	`~/.local/share/rezeptor/sync-state.json`

In the GUI: Help → Update recipes… (also checked quietly after startup). Changes need confirmation before apply.

Catalog fields for sync:

Field	Meaning
`min_app_version`	Recipe needs this Rezeptor version (core APIs). Older apps see blocked — update the app.
`deprecated`	Recipe should not be newly installed; installed data is not auto-deleted.

Recipe options (Medizin)¶

Lasting per-recipe settings (not “install once”). The Medizin button (icon kit-medical) next to More opens a dialog with checkbox + explanation. Values in {data_root}/options.env steer install/repair/launch.

Only use when the option changes behaviour (e.g. opt-out). Not for actions Install/Repair already perform.

options:
  - id: nvidia_libs
    env: PREMIERE_NVIDIA_LIBS
    type: bool
    default: true
    when: nvidia
    label: { de: "…", en: "…" }
    tip: { de: "…", en: "…" }

Multiple sources (multi-source)¶

Rezeptor can merge recipes from several sources:

Source	Typical use
Local repo	Official + `recipes/community/`
Release recipes bundle	Overlay sync for official recipes
`catalog.json` on GitHub	Remote index for community / BYOS installs

Check trust

Recipes from external sources run scripts on your system. Review recipe.yml and hooks before installing. The GUI may warn when trust differs (trust).

Hide vs. uninstall¶

Action	Effect
Hide	Recipe disappears from the list; data remains (`~/.local/share/wine-software/<id>/`). Show again later.
Uninstall	Runs `uninstall.sh` and fully removes Rezeptor state, shortcuts, and the chosen `data_root` (`recipe_hooks::purge_recipe_data`).

Portable folders or Steam games outside data_root are left untouched on uninstall (see STEAM-WRAPPER.md).

Runtime: Proton-GE¶

All recipes require Proton-GE (core/runtime.lock). No system-Wine fallback in recipe scripts. Graphics DLLs come from wine_runtime::deploy_proton_graphics_dlls() — no winetricks-dxvk.

More: ENTWICKLER.md · TRUST.md · UNINSTALL.md