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