A Rails 8 web application that demonstrates how to integrate with the Open Wearables platform - a unified API for connecting and syncing health data from multiple wearable devices.

• Open Wearables Documentation
• Open Wearables GitHub

This app is a reference implementation showing three core integration patterns:

1. User auth flow with wearable providers - Generate connection links via the Open Wearables API, redirect users to authenticate with their wearable provider (Garmin, Whoop, Oura, Polar, Suunto, Strava, etc.), and handle the OAuth callback.
2. Pulling data from the Open Wearables API - Fetch normalized health data (heart rate, sleep, activity, steps, HRV, recovery, strain) through the unified REST API.
3. Receiving webhooks from Open Wearables - Accept incoming webhook notifications when new health data or health insight automations are triggered.

• Unified API: Single REST API (authenticated via X-Open-Wearables-API-Key header) that normalizes data across all wearable providers.
• Providers: Wearable platforms the user connects - cloud-based (Garmin, Whoop, Polar, Suunto, Strava, Oura) and SDK-based (Apple HealthKit, Samsung Health, Google Health Connect).
• Connect flow: Generate a connection link for a user -> user authenticates with their provider via OAuth -> data syncs automatically -> access via API.
• Health data types: Activity/workouts, sleep (stages, efficiency, duration), biometrics (heart rate, HRV), recovery scores, strain metrics, steps.

For more details, see the Open Wearables docs and API reference.

• Ruby 3.3.1 / Rails 8.0.5
• SQLite3 (primary, cache, queue, cable)
• Hotwire (Turbo + Stimulus) with ImportMap
• Tailwind CSS
• Propshaft asset pipeline
• Solid Queue, Solid Cache, Solid Cable
• Puma with Thruster

Copy the example env file and fill in your API keys:

cp .env.example .env

All you need is Docker.

cp .env.example .env       # fill in your API keys
docker compose up           # build image, install gems, migrate DB, start server

The app will be available at http://localhost:3100. Gem changes in Gemfile are picked up automatically on the next docker compose up.

Requires Ruby 3.3.1 and SQLite3 installed on your machine.

./bin/setup    # Install deps, create DBs, start server
./bin/dev      # Start dev server with Tailwind watcher (port 3000)

The app ships with a production-ready Dockerfile, so Railway can build and deploy it directly.

1. Go to railway.app and log in.
2. Click New Project -> Deploy from GitHub Repo and select this repository.

SQLite databases live in storage/, so you need a volume to persist them across deploys:

1. In your Railway service, go to Settings -> Volumes.
2. Add a volume mounted at /rails/storage.

In the Variables tab, add:

Railway assigns a dynamic port via the PORT env var. Either set PORT=80 in Railway variables, or override the start command to:

./bin/thrust ./bin/rails server -p $PORT

In Settings -> Networking, click Generate Domain to get a *.up.railway.app URL.

Railway will automatically build from the Dockerfile on every push to your main branch.