Self hosted FLOSS fitness/workout tracker

Original Article ↗ Hacker News Discussion ↗

Apple Health and Integrations

  • Lack of Apple Health import is seen as a major drawback; some view this as a blocker for adoption.
  • Others note that the project is FOSS, so integrations like Apple Health could be community-built; an issue for this exists in the mobile client repo.

UI/UX and Feature Feedback on wger

  • Users describe the UI as clunky and confusing, especially on mobile.
  • Pain points: hard to see which set/series you’re currently on, rest timer issues on Android when app focus changes, some features only available in the web UI, and missing exercise images.
  • Despite this, some users still find it useful and continue using it; contributing improvements via PRs is encouraged, though not everyone feels up to mobile dev work.
  • A hosted instance to try before self-hosting is requested.

FLOSS / FOSS / Open Source Terminology Debate

  • Long subthread debating meanings of “Free,” “Libre,” and “Open Source”:
    • Clarification that “free” in this context is about freedom, not price; “libre” is added to avoid ambiguity.
    • Some argue the terms in FLOSS largely overlap; others insist they don’t and give examples:
      • Paid access to binaries while source is free to compile.
      • Licenses that are open source but not “free/libre” (e.g., with non-commercial or no-military-use clauses; NASA Open Source Agreement).
      • Software that is free of charge but neither open source nor libre.
  • Disagreement over the history and intent of “FLOSS” and how strictly “libre” should be tied to specific licenses.

Hosted vs Local-First vs “Self-Hosted”

  • One group questions why a workout tracker “requires” a server instead of being local-first with optional sync.
  • Others argue for server-based designs:
    • Multi-device access and syncing (phone, laptop, watch).
    • Easier integration with wearables and shared databases.
    • Better control for developers (central algorithms, debugging, upgrades).
  • Counterpoint: for manual workout logging, phones already have ample storage/compute, so server-by-default feels unnecessary; “self-hosted but server-required” is contrasted with local-first approaches.

Easier Self-Hosting and One-Click Installs

  • Question raised about a “one-click, per-request-priced” cloud for self-hosted apps.
  • Constraints noted: most self-hosted apps expect always-on servers with persistent databases and disk, making serverless-style billing difficult.
  • Mentioned solutions/approaches: PikaPods, Sandstorm, YunoHost, TrueNAS apps, NixOS, Cloudron, Linode marketplace, cPanel/Fantastico, Coolify/Dokploy, Portainer + Docker on a single VPS or home server.

Privacy-Friendly Wearables and Alternatives

  • Desire for privacy-friendly fitness wearables that don’t stream all data to vendor servers.
  • Suggestions:
    • Simple BLE heart-rate straps (e.g., Garmin chest strap) that broadcast directly to phone/PC and support continuous HR and HRV.
    • Garmin watches used offline, with data pulled via USB to a PC.
    • Bangle.js 2 as an open, hackable watch.
    • GoldenCheetah for local analysis of sensor data on PC.
  • Some users avoid phone apps altogether in the gym due to lock-in and distraction, preferring paper or e-ink note devices.

Alternative Fitness / Tracking Apps

  • Other self-hosted or privacy-friendly options mentioned:
    • Ryot (general-purpose tracker with workout and media tracking, features can be disabled).
    • Liftosaur (powerful strength-training app with scripting; some find UI janky and partially paywalled).
    • Iron for iOS, LiftLog, and FitNotes for Android (not FOSS but reportedly offline and non-tracking).