An F-Droid repository and a SideStore/AltStore source for kapsikkum's apps, hosted on GitHub Pages at https://kapsikkum.github.io/apps/.
| URL | |
|---|---|
| F-Droid / Droid-ify / Neo Store | https://kapsikkum.github.io/apps/fdroid/repo |
| Obtainium | no repository needed: add the app's GitHub repo, or use the links on the landing page. Pick the arm64 APK for Mudrix. |
| SideStore / AltStore | https://kapsikkum.github.io/apps/sidestore.json |
Scan with F-Droid to add the repository (the code includes its key fingerprint):
Fingerprint: E1329DD0AC232D12B7506064218F908906A4ED23BB7A4BFE2A1FB841EC99BECB
Apps: Mudrix, PhotoScout, opnscrl.
apps.json lists the apps and the release assets to use. .github/workflows/update.yml runs
scripts/build.mjs, which downloads each app's latest APK, writes the F-Droid metadata and builds the SideStore
source (IPAs are linked from the GitHub release, not copied). fdroid update then signs the F-Droid index, and
the result is deployed to Pages. It runs every 6 hours, on repository_dispatch of type app-release, and by hand.
SideStore's "What's new" for a version is that release's notes, cleaned up by scripts/notes.mjs. The mobile
releases have no notes of their own, so "notes" in apps.json names the repo (the web client) whose release of the
same version is used instead.
Add an entry to apps.json (repo, the release tag or latest-stable, the APK and IPA asset names, the Android
package and iOS bundle id). Asset names may contain {version} for releases that put the version in the file name. Only the latest release of each app is kept in the F-Droid repo.
- The F-Droid repo key is the
FDROID_KEYSTORE_BASE64/FDROID_KEYSTORE_PASSWORDsecrets. Keep a backup of the keystore: if it changes, everyone has to remove and re-add the repo. - F-Droid only installs updates signed by the same key as the installed app, so each app's APK has to be signed with a stable key in its own release workflow.
- IPAs are unsigned; SideStore signs them on the device.