Migrating from Capgo

Move a Capacitor app from Capgo to Hotrail by changing three URLs, then swap the plugin at your next store build.

How it works

Hotrail answers the documented self-hosted update protocol used by @capgo/capacitor-updater. Your installed apps keep their plugin and only talk to different URLs. You do not need a new store build to start.

Step 1: set up the project

Run init in your project. It detects your appId and web directory, writes hotrail.json and creates a signing key. If it finds @capgo/capacitor-updater in package.json it prints a migration note.

bash

npx @buffersol/hotrail init

Step 2: point the three URLs

In your Capacitor config for @capgo/capacitor-updater, set updateUrl, statsUrl and channelUrl to your Hotrail URLs. Nothing else in your app code changes.

text

updateUrl:  https://hotrail.buffersoltech.com/api/v1/updates/check
statsUrl:   https://hotrail.buffersoltech.com/api/v1/updates/stats
channelUrl: https://hotrail.buffersoltech.com/api/v1/updates/channel

Step 3: upload and release

Upload a build, then release it to a channel. Start with a small percentage if you want to watch the first rollout.

bash

npx @buffersol/hotrail upload
npx @buffersol/hotrail release --channel production --percent 10

Step 4: swap the plugin later

At your next store build, replace @capgo/capacitor-updater with @buffersol/hotrail-updater. That plugin adds signed delta downloads and automatic crash revert. Until then the Capgo plugin keeps working against Hotrail with checksum verification only.

The Swift and Kotlin code of our plugin is written but has not been compiled or tested on devices yet, and its CI workflow has not run green yet. If that matters for your release, stay on the Capgo plugin and only change the URLs for now.