feat: add Fly.io deployment config and GitHub Actions cron

Add fly.toml for one-command Fly.io deployment with persistent
SQLite volume, and a GitHub Actions workflow that triggers hourly
data collection via the /api/cron endpoint.

Made-with: Cursor

Author: ofershap

.github/workflows/cron.yml

@@ -0,0 +1,17 @@
+name: Scheduled collection
+
+on:
+  schedule:
+    - cron: "0 * * * *"
+  workflow_dispatch:
+
+jobs:
+  collect:
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    steps:
+      - name: Trigger collection and detection
+        run: |
+          curl -sf -X POST "${{ secrets.DASHBOARD_URL }}/api/cron" \
+            -H "x-cron-secret: ${{ secrets.CRON_SECRET }}" \
+            -H "Content-Type: application/json"

README.md

@@ -277,13 +277,24 @@ volumes:
 
 </details>
 
-### Cloud platforms
+### Fly.io (recommended free option)
 
-Any platform that supports Docker + persistent volumes works. Tested with:
+```bash
+fly launch --copy-config          # creates the app from fly.toml
+fly volumes create tracker_data --region ams --size 1
+fly secrets set CURSOR_ADMIN_API_KEY=your_key CRON_SECRET=your_secret
+fly deploy
+# Dashboard at https://your-app.fly.dev
+```
+
+Set up hourly collection by adding `DASHBOARD_URL` and `CRON_SECRET` as [GitHub Actions secrets](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions) — the included `.github/workflows/cron.yml` workflow triggers `/api/cron` every hour.
+
+### Other cloud platforms
+
+Any platform that supports Docker + persistent volumes works:
 
 - **[Render](https://render.com)** — use the deploy button above, or `render.yaml` in this repo
 - **[Railway](https://railway.app)** — create a project from this repo, attach a volume at `/app/data`
-- **[Fly.io](https://fly.io)** — deploy with `fly launch`, create a volume for `/app/data`
 
 > **Note:** Vercel is not supported — SQLite requires a persistent filesystem that Vercel's serverless functions don't provide.
 

fly.toml

@@ -0,0 +1,25 @@
+app = "cursor-usage-tracker"
+primary_region = "ams"
+
+[build]
+
+[env]
+  PORT = "3000"
+  NODE_ENV = "production"
+  DATABASE_PATH = "/app/data/tracker.db"
+
+[http_service]
+  internal_port = 3000
+  force_https = true
+  auto_stop_machines = false
+  auto_start_machines = true
+  min_machines_running = 1
+
+[[vm]]
+  memory = "256mb"
+  cpu_kind = "shared"
+  cpus = 1
+
+[[mounts]]
+  source = "tracker_data"
+  destination = "/app/data"