BikeControl (SwiftControl)
使用 Zwift Click、Zwift Play、Shimano Di2,或任何藍牙控制器搭配 MyWhoosh、Rouvy、Zwift 等。可於 iOS、Android、Windows 與 macOS 免費試用。
AI 翻譯
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證A hockey podcast site.
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗This repository contains the FHFHockey web application, content studio, serverless functions, and database assets. There is no root package manifest; run commands from the owning workspace described below.
The primary application requires Node 22.11.0 from web/.nvmrc.
For web/, npm plus web/package-lock.json is the sole
package-manager authority.
cd web
nvm use
npm ci
npm run dev
See web/README.md for the stable watcher fallback, tests,
browser verification, and Supabase CLI workflow.
web/ — the primary Next.js application, API routes, scripts, unit
tests, and Playwright tests. Its manifest is web/package.json.cms/ — the Sanity Studio. Its independent manifest provides
npm run dev; see cms/README.md. It does not share the web
lockfile.functions/ — the separately deployed Python/Node serverless
boundary. Its documented local launcher runs from the repository root:
yarn vercel dev --cwd functions --listen 3003. See
functions/README.md; this command is intentionally
separate from the web package-manager contract.supabase/ — local Supabase configuration and the current
migration chain. Run the documented CLI wrapper from web/; do not apply
remote migrations as part of setup.migrations/ and sql/ — additional SQL assets with
distinct historical/workflow ownership. Confirm the relevant migration tree
before using or changing either directory..github/workflows/ — CI and scheduled-workflow
definitions; these are operational configuration, not local setup scripts.Repository-wide contribution and safety rules live in
AGENTS.md. Package-level documentation remains authoritative for
detailed commands so this entrypoint can stay concise.
The checked-in VS Code MCP configuration is intentionally inert and starts no shared server. Contributors may configure reviewed MCP tools in their personal editor settings; package downloads, network access, and credentials remain an explicit per-contributor trust decision and must not be committed here.