MMA LiveSim
Free UFC DFS optimizer and MMA fight simulator for DraftKings. Live win probabilities for every lineup, plus post-contest EV, ownership, and optimal lineups.
翻译准备中
尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证FitGlue is a serverless fitness data aggregation and routing platform built on Google Cloud Platform. It ingests workout data from multiple sources (Hevy, Keiser, Fitbit), enriches it with standardized formats (FIT files), and routes it to connected services like Strava.
翻译准备中
取自仓库 README
正在加载完整 README。
查看完整 README ↗FitGlue is a fitness data aggregation and routing platform built on Google Cloud Platform. It ingests workout data from multiple sources (Hevy, Fitbit, Strava, Intervals.icu, GitHub, parkrun), enriches it through configurable pipelines, and routes it to connected services.
FitGlue uses a domain-service architecture: 11 Go Cloud Run services communicating via gRPC, with a thin API gateway layer for HTTP clients.
┌─────────────────┐ ┌──────────────────────┐
│ Data Sources │─────▶│ service.api.webhook │
│ (Hevy/Strava/ │ │ (HMAC / OAuth auth) │
│ Fitbit / etc.) │ └──────────┬────────────┘
└─────────────────┘ │ Pub/Sub
▼
┌──────────────────────┐
│ service.pipeline │
│ (enrich, split, │
│ route) │
└──────────┬────────────┘
│ Pub/Sub
▼
┌──────────────────────┐
│ service.destination │
│ (upload to Strava, │
│ TrainingPeaks, etc.)│
└──────────────────────┘
API gateways sit in front for HTTP clients:
service.api.client — the owner's tools: Jarvis, fitgluectl, fitglue-mcp (static bearer token, see Security)service.api.public — Unauthenticated (showcase)Domain services own their Firestore data and expose gRPC interfaces:
service.user, service.pipeline, service.activityWorker services consume Pub/Sub topics:
service.destination — uploads to Strava, TrainingPeaks, Fitbit, etc.See Architecture Overview for the full system diagram.
| Component | Technology |
|---|---|
| Language | Go 1.25+ |
| Compute | Cloud Run (Docker containers) |
| Messaging | Cloud Pub/Sub |
| Database | Cloud Firestore |
| Storage | Cloud Storage (FIT files, GCS payloads) |
| Inter-service | gRPC (protobuf) |
| CI/CD | GitHub Actions on PRs; CircleCI deploy on main until F4 (see CI/CD) |
| Infrastructure | Terraform |
| Observability | structured slog; Sentry optional via a single SENTRY_DSN |
protoc (Protocol Buffers compiler)# Install Go dependencies and generate proto stubs
make setup
make generate
# Build all services
make build
# Run unit tests
make test
# Start local development stack (all 11 services)
make local
See Local Development for detailed instructions.
fitglue-server/
├── src/
│ ├── go/ # Go monorepo
│ │ ├── services/ # 11 Cloud Run services (main.go per service)
│ │ ├── internal/ # Domain logic (owned by services)
│ │ ├── pkg/ # Shared packages (proto stubs, integrations)
│ │ ├── cmd/ # CLI tools (fit-gen, fit-inspect)
│ │ └── tests/e2e/ # Cucumber/godog E2E tests
│ └── proto/ # Protocol Buffer definitions
├── terraform/ # Infrastructure as Code
├── docs/ # Documentation
│ ├── api/ # OpenAPI spec (auto-generated)
│ ├── architecture/ # Architecture guides
│ ├── decisions/ # ADRs + history
│ ├── development/ # Dev guides
│ ├── guides/ # How-to guides
│ ├── infrastructure/ # CI/CD, Terraform
│ └── reference/ # Errors
├── scripts/ # Dev and CI scripts
└── Makefile # Build, test, generate, deploy commands
fitgluectl connect / connections, per-provider webhook notesmain deploy that F4 retiresThis is a personal project, but suggestions and feedback are welcome via issues.
MIT