No description

Find a file

Claude 15b7450c34 Release 0.1.1+2		2026-08-30 04:00:21 +02:00
public	Release 0.1.1+2	2026-08-30 04:00:21 +02:00
.dockerignore	Somewhere for the app to look for a newer version of itself	2026-08-30 03:53:38 +02:00
Dockerfile	Somewhere for the app to look for a newer version of itself	2026-08-30 03:53:38 +02:00
nginx.conf	Somewhere for the app to look for a newer version of itself	2026-08-30 03:53:38 +02:00
README.md	Somewhere for the app to look for a newer version of itself	2026-08-30 03:53:38 +02:00
release.py	Release 0.1.0+1	2026-08-30 03:53:55 +02:00

README.md

media-updates

What the amber-adult app checks at launch to find a newer build of itself.

Two files behind nginx: manifest.json, and the APK it names. No authentication, deliberately — there is no account to check against and the APK holds no secret. The credential in that app is the addon URL, which lives in the device keystore and never leaves it.

Publishing a release

./release.py ../amber-adult/build/app/outputs/flutter-apk/app-release.apk "what changed"

It reads the version and build number out of amber-adult/pubspec.yaml, copies the APK in under a versioned name, writes manifest.json, and commits. Push, and Coolify redeploys.

The APKs are committed. At ~34MB and a handful of releases a year that is the cheaper trade against standing up artifact storage for one app; if the repository ever gets uncomfortable, the history is disposable — only the newest artifact is ever fetched.

The manifest

{
  "version": "0.1.0",
  "buildNumber": 1,
  "notes": "…",
  "sha256": "…64 hex…",
  "size": 34210000,
  "url": "https://media-updates.petruzalekr.cz/media-1.apk"
}

The client refuses anything it cannot act on: an equal or older buildNumber, a missing url, or a sha256 that is not 64 characters. The download is checked against that digest before it reaches the installer.