# Release keystore The actual `.jks` files in this directory are gitignored (see `/home/nick/.gitignore` / `.gitignore` rules under "Release keystore"). This directory ships with **no checked-in keys** — every developer (and the CI runner) is expected to generate their own. ## Generate a local dev keystore This is the keystore the project's default `signingConfigs.release` points at. Replace before publishing to any app store. ```bash keytool -genkey -v \ -keystore release.jks \ -keyalg RSA -keysize 2048 -validity 10000 \ -alias incido \ -storepass incido_dev_keystore \ -keypass incido_dev_keystore \ -dname "CN=Incido Dev, OU=Local, O=Incido, L=Local, ST=Local, C=NZ" ``` The store password and key password are both `incido_dev_keystore` — change them before publishing. ## For Play Store / F-Droid distribution Generate a **separate** production keystore and store the credentials outside the repo (CI secrets, password manager, etc.). Replace the `signingConfigs.release` block in `app/build.gradle.kts` with one that reads from `~/.gradle/gradle.properties` or environment variables so the real passwords are never committed. Do **not** lose your production keystore — without it you can never publish updates under the same `applicationId`/`packageName`. ## CI Gitea Actions (`/.gitea/workflows/build.yml`) currently only builds the **debug** APK, which uses the auto-generated Android debug keystore. Add a `release` job once you have secrets for the production key.