feat: Trafero v0.2.0 - Tdarr v2 native Android client with slow-connection resilience

Full client for the Tdarr /api/v2 JSON API (jobs, library, nodes, stats, logs, settings, flows, multi-server switcher) plus v0.2.0 resilience: per-server timeout + slow-connection mode, retry-with-backoff on read polls, last-good-data + reconnecting chip, 60s poll backoff after repeated failures, and keep-alive eviction on app resume.

Includes GPL-3.0 licensing (LICENSE/NOTICE), README, CONTRIBUTING, PREVIOUS_HISTORY, issue/PR templates, CI release-notes script, keystore docs and the vendored OpenAPI 2.0 spec.
This commit is contained in:
nick committed 2026-09-21 17:46:29 +12:00
commit 312858e8f6
50 files changed
+4446

No files matched your search

+42
View File
@@ -0,0 +1,42 @@
# 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/release.jks` (same parameters as above) 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.
**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.