[stretch0]

What changed

• deploy/fly/fly.toml: a real instance, unlike the demo's. The 0.3 release line, data on a volume at /data, one always-on machine (so syncs, weather and reminders keep running), INVITE_ONLY and TRUST_PROXY on.
• docs/FLY.md: setup in four steps, your own domain (and why to choose it before passkeys), upgrades, backups (Fly's daily snapshots plus downloading a backup.js copy), password resets and what to know. Linked from the README's self-hosting section.

Tested

A throwaway openrun-trial app built from this config, now deleted:

• The first start applied 9 database updates and handed /data (root-owned on a Fly volume) to the node user.
• With real data (84 synced runs, a club with 8 runs), a machine restart and an upgrade from 0.2.0 to 0.3.0 ("Applied 1 database update") left every table's row count, all 85 file checksums and the push keys unchanged, and the sign-in session survived.

Not tried: restoring a snapshot, downloading a backup over fly ssh sftp, club logos and push delivery on Fly.

🤖 Generated with Claude Code