Files
Trafero/keystore/README.md
T
nick b8ac68b363
dev / Build debug APK (push) Successful in 15s
release / Build & attach release APK (push) Successful in 25s
ci: use a Trafero-specific persistent CI keystore path
The runner cache already held a release.jks minted by another project with a different store password, so packageRelease failed with "keystore password was incorrect". Mint and reuse trafero-release.jks instead.
2026-09-21 18:02:14 +12:00

45 lines
1.7 KiB
Markdown

# Release keystore
The `.jks` files in this directory are gitignored — this repo ships with
**no checked-in keys**. Every developer (and the CI runner) generates
their own; see `.gitignore` rules under "Release keystore".
## Generate a local dev keystore
This is the keystore `signingConfigs.release` in `app/build.gradle.kts`
points at. Run from this directory:
```bash
keytool -genkey -noprompt -v \
-keystore release.jks \
-keyalg RSA -keysize 2048 -validity 10000 \
-alias trafero \
-storepass trafero_dev_keystore \
-keypass trafero_dev_keystore \
-dname "CN=Trafero, OU=Local, O=Trafero, L=Local, ST=Local, C=NZ"
```
Store and key passwords are both `trafero_dev_keystore` — change them
before publishing anywhere real.
## CI (Gitea Actions)
`release.yml` mints one persistent keystore on the runner at
`/var/lib/gitea-runner/work/trafero-release.jks` (same parameters as
above, except `CN=Trafero CI`) and copies it to `keystore/release.jks`
for every build, so all CI release APKs share one signing key and users
can upgrade in place. The file is project-specific (`trafero-` prefix)
because the runner cache directory is shared between repositories.
**Important:** locally-built (and debug) APKs have a *different*
signature from CI release APKs — installing a CI release build over a
debug build requires an uninstall first.
## For Play Store / F-Droid distribution
Generate a **separate** production keystore, keep it outside the repo,
and switch `signingConfigs.release` to read credentials from
`~/.gradle/gradle.properties` or environment variables. Do **not** lose
the production keystore — without it you can never publish updates under
the same applicationId.