個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證A beautiful, self-hosted recipe app
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗[!WARNING] Sizzle is very early in development. Expect rough edges and breaking changes between releases.
Sizzle starts in the dark Sunny side up theme. Pick another look, or light, dark or auto, any time
from the Appearance button in the header. Want something else? Set SIZZLE_THEME_EDITOR=true to turn on the theme editor, then
Customize any theme and save it as your own. Built-in themes live in config/themes.json; see
docs/themes.md to add one.
With Docker running, start a separate trial at http://localhost:3001. No account or AI key is needed. Only this computer can connect; the trial has its own storage volume.
docker run -d --name sizzle-try \
-p 127.0.0.1:3001:80 \
--read-only --security-opt no-new-privileges:true \
--tmpfs /rails/tmp:uid=1000,gid=1000,mode=0755 \
--tmpfs /tmp:mode=1777 \
-v sizzle-try-storage:/rails/storage \
ghcr.io/leemac/sizzle:latest
Allow a moment for the first start, then open the address above. You can write a recipe or optionally load the bundled sample cookbook. Browse a recipe, try cooking mode, and use Settings → Your data → Download cookbook.
docker stop sizzle-try stops the trial and keeps your recipes; docker start sizzle-try
resumes it. See the trial guide
for removal instructions. To use Sizzle from your phone, follow the server installation below.
You need Docker with Compose on a home server, NAS, Raspberry Pi 4/5 or VPS. Images are published
for amd64 and arm64.
Download the compose file and settings from the latest release:
mkdir sizzle && cd sizzle
curl -fsSLO https://github.com/leemac/sizzle/releases/latest/download/docker-compose.yml
curl -fsSL https://github.com/leemac/sizzle/releases/latest/download/env.example -o .env
Generate a share API token:
openssl rand -hex 32
Open .env in a text editor and paste the generated value after SIZZLE_API_TOKEN=.
Save the file before continuing. This token protects the share API, not the web UI.
SIZZLE_HOSTS: only if you'll open Sizzle at a domain name like recipes.example.com.
IP addresses, bare hostnames and .local, .lan, .home.arpa and .ts.net names work
without it.ANTHROPIC_API_KEY: optional. Each AI extraction is a paid Claude request.Every other setting is explained in .env.example.
Start it:
docker compose up -d --wait
When the command succeeds, open http://<your-server>:3000 (or http://localhost:3000 on the
server itself). Write a recipe or import a recipe link first, then choose Share from your phone
to set up sharing. If startup fails, see troubleshooting.
After changing .env, run docker compose up -d --force-recreate --wait to apply the settings.
docker compose restart does not reload .env.
[!IMPORTANT] Sizzle has no login yet. Keep it on your home network or a private network like Tailscale, and read SECURITY.md before exposing it anywhere else.
To upgrade, run docker compose pull && docker compose up -d. Everything Sizzle stores lives in
the sizzle-storage volume, so back that up. Self-hosting covers pinning a
version, upgrades, backups and building from source.
bin/setup --seed # needs the Ruby in .ruby-version, Node 22 and libvips
bin/dev # http://localhost:3000
npx playwright install chromium # once, for browser tests
bin/ci # all checks and tests
Sizzle is built in the open as a software factory: well-specified issues are worked by AI agents and reviewed by people. Start with AGENTS.md for the architecture, conventions and security rules, then CONTRIBUTING.md and docs/factory.md.
AGPL-3.0. Run, modify and share Sizzle freely; if you offer a modified version as a service, share your changes. Bundled assets such as the Bricolage Grotesque font keep their own licenses: see THIRD_PARTY_NOTICES.md.