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.