Sizzle v0.3.0

Sizzle is early in development. Expect rough edges and breaking changes between releases.

What's new

• Pick a theme and light, dark or automatic mode for each browser. Enable the optional editor to create shared custom themes. #50
• Use SOS to find recipes for the current meal, with seasonal recipes first. Edit meal times and seasons on your recipes. #51
• Set cooking text size, screen wake lock, recipe order and Claude import permission in Settings. Download a portable cookbook archive with recipes, photos and cooking history. #56
• Install and connect the optional prebuilt iPhone Shortcut without copying the server API token; revoke individual connections from Sizzle. #52
• Printed recipes show when they were added, cooked and printed. The logo gains a hover animation, and the landing page has refreshed seasonal recipe previews. #54, #55, #57

Fixes

• Share an import budget across web requests, the API and retries; bound image download attempts and redact imported content and URLs from application logs. #53

Upgrade

Before upgrading, stop Sizzle, copy the complete storage volume using the backup procedure, then restart it. Do not copy a live SQLite database.

Set SIZZLE_VERSION=0.3.0 in .env, then run docker compose pull && docker compose up -d. Four migrations run automatically: custom themes, per-import AI permission, shortcut connections, and recipe meal times/seasons. Existing recipes receive initial meal times from their course and seasons from matching tags.

The Compose files and dependency locks are unchanged. Two optional settings are new and default off: SIZZLE_THEME_EDITOR=true and SIZZLE_SHORTCUT_PAIRING=true. Add either to .env and recreate the container to enable it. Anyone who can reach the web UI can edit shared themes or pair shortcuts when enabled. The existing token-protected script API remains available.

Web imports now ask for Claude permission by default; browser Settings can allow automatic fallback. Phone and script imports retain the server's AI configuration.

To roll back, stop Sizzle, restore the complete pre-upgrade storage backup and pin the previous image version. Changing the image alone does not undo database migrations.

Known limitations

• Sizzle has no login. Keep it on a trusted private network or behind an authenticating reverse proxy.
• Cookbook exports are bounded portable downloads, not complete server backups; importing an export into Sizzle is not yet supported.
• Keeping the screen awake requires browser support and HTTPS or localhost.
• iPhone Shortcut installation and manual execution have been confirmed; end-to-end pairing and recipe import on a physical iPhone remain unverified. The shortcut stores one cookbook connection per Apple account in iCloud Drive; reverse-proxy authentication may need additional setup.

Full changes: v0.2.0...v0.3.0