Repository navigation
Upgrading
For script changes that don't involve new config keys, cron timing changes, or path changes, scp the updated scripts directly. No install.sh re-run needed.
My Activities + HTML helpers:
scp strava-my-activities.sh root@192.168.1.1:/usr/bin/strava-my-activities `
&& scp strava-lib.sh root@192.168.1.1:/usr/bin/strava-lib.sh `
&& scp strava-my-html-dashboard.sh strava-my-html-detail.sh strava-my-html-bike.sh strava-my-html-stats.sh root@192.168.1.1:/usr/bin/ `
&& ssh root@192.168.1.1 strava-my-activitiesHealthSync (also push strava-lib.sh — it holds the shared weather backfill):
scp healthsync-activities.sh root@192.168.1.1:/usr/bin/healthsync-activities `
&& scp strava-lib.sh root@192.168.1.1:/usr/bin/strava-lib.sh `
&& ssh root@192.168.1.1 healthsync-activitiesClub leaderboard:
scp strava-leaderboard.sh root@192.168.1.1:/usr/bin/strava-leaderboard `
&& ssh root@192.168.1.1 strava-leaderboardEmail / cron-guard scripts (push both together; no manual run needed):
scp strava-cron-guard.sh root@192.168.1.1:/usr/bin/strava-cron-guard `
&& scp strava-email-monthly.sh root@192.168.1.1:/usr/bin/strava-email-monthly `
&& scp strava-email-monthly.sh root@192.168.1.1:/usr/bin/strava-email-weekly `
&& ssh root@192.168.1.1 "chmod 0755 /usr/bin/strava-cron-guard /usr/bin/strava-email-monthly /usr/bin/strava-email-weekly"Run this after changes to install.sh, new config keys, or path changes. Re-running install.sh is idempotent: it overwrites all binaries, leaves existing config files untouched, and replaces the cron lines.
scp -r . root@192.168.1.1:/tmp/strava
ssh root@192.168.1.1 sh /tmp/strava/install.sh
strava-leaderboard # verify
strava-my-activities # verifyOpenWrt's sysupgrade wipes the overlay filesystem and reinstalls packages from scratch — nothing installed by install.sh survives by default. To protect your scripts, configs, and state data, list the paths in /etc/sysupgrade.conf — OpenWrt backs them up before flashing and restores them after.
install.sh sets this up for you — no manual steps are needed after a firmware upgrade:
- It stages a copy of the repo in
<STRAVA_MY_STATE_DIR>/install-bundle(override withSTRAVA_BUNDLE_DIR) — keep this on persistent storage such as a USB disk. - It installs
/etc/strava-restore.sh+/etc/strava-restore.confand adds a line to/etc/rc.local. - It appends every installed path, the state dirs, and the restore files to
/etc/sysupgrade.conf.
On the first boot after a sysupgrade, the hook notices /usr/bin/strava-lib.sh is gone, waits for the network, reinstalls the packages, re-runs the bundled install.sh, then regenerates the pages with strava-my-activities, strava-leaderboard and healthsync-activities (HealthSync is skipped while its config is missing or still the template). On a normal boot it does nothing. Progress is logged to strava-restore.log in the parent of the bundle directory (e.g. /mnt/sda5/strava-my-activities/strava-restore.log).
Requirements: working internet on first boot (packages are downloaded) and the USB disk mounted (the hook waits up to 5 minutes for it). Re-run install.sh after updating the repo so the bundle stays current.
cat >> /etc/sysupgrade.conf << 'EOF'
/usr/bin/strava-leaderboard
/usr/bin/strava-my-activities
/usr/bin/healthsync-activities
/usr/bin/strava-cron-guard
/usr/bin/strava-email-monthly
/usr/bin/strava-email-weekly
/usr/bin/strava-lib.sh
/usr/bin/strava-my-html-dashboard.sh
/usr/bin/strava-my-html-detail.sh
/usr/bin/strava-my-html-bike.sh
/usr/bin/strava-my-html-stats.sh
/etc/strava-leaderboard.conf
/etc/strava-my-activities.conf
/etc/healthsync-activities.conf
/usr/lib/strava-leaderboard
/usr/lib/strava-my-activities
/usr/lib/healthsync
EOF/etc/sysupgrade.conf itself is always preserved by sysupgrade — this is a one-time step.
Web dir links: if both
STRAVA_MY_WEB_DIRandHEALTHSYNC_WEB_DIRare relocated to different directories,install.shlinks/www/strava/meto whichever has the neweractivities.json, so a stale HealthSync dir can't hide your My Activities pages. If/strava/me/shows an empty listing, checkls -l /www/strava/me.
| What needs restoring | Plain sysupgrade + keep settings | Attended Sysupgrade (ASU) + keep settings |
|---|---|---|
| Scripts / configs / state | Automatic (from backup) | Automatic (from backup) |
curl, jq, ca-bundle
|
Must reinstall | Baked into firmware — nothing to do |
| Cron entries | Automatic (cron package registers /etc/crontabs/) |
Automatic |
/www symlinks + CGI |
Must run install.sh |
Must run install.sh |
Plain sysupgrade — post-upgrade steps:
# Re-install packages (wiped by sysupgrade)
opkg update && opkg install curl jq ca-bundle
# Restore /www symlinks and CGI (copy repo to /tmp/strava first)
sh /tmp/strava/install.shAttended Sysupgrade (ASU) — post-upgrade steps:
# Packages are already in the new firmware; just restore /www symlinks and CGI
sh /tmp/strava/install.shState and configs are already back (restored from the sysupgrade backup). install.sh won't overwrite existing configs, so your secrets and activity history are safe.