Deployments reachable outside a trusted LAN need some form of access
control. Set FUELISH_API_KEY and the server requires a matching
X-API-Key header on /jobs; unset, behavior is unchanged (no auth).
The Android app gets a matching Settings field. This only checks the
key - TLS termination is left to a reverse proxy in front of the
server, not handled here.
manual CI publishes
- Settings: prefill an editable example server URL, add a "Test
connection" button
- Front page now shows the receipts list (Overview) with a column
header and an empty-state message
- Add a connection status bar (polls /health) shown on every screen
- Capture: add "Choose from gallery" alongside the camera
- Add an in-app "App log" screen; ApiClient/CaptureViewModel/
OverviewViewModel/ConnectionStatusViewModel now log key events,
including the actual connection-failure reason (not just pass/fail)
- .gitea/workflows/build.yml: publish to dl.ladkau.de on a manual
"Run workflow" dispatch too, not just push
- README.md: document the CI secrets (REGISTRY_USER/PASSWORD,
DL_SFTP_KEY) that must be configured in Gitea, separate from the
local registry.env
- build-image/: Dockerfile bundling JDK 17, the Android SDK, and
Node.js (needed by Gitea's JS-based actions) - the app has no
native code, so no NDK
- build-image.sh/upload-image.sh: extended to also build/push this
image alongside the existing OCR pipeline tools image
- run-image.sh: runs `make android` inside the image against a live
checkout, for a CI-equivalent local build
- Makefile: `make android` builds and versions a release APK into
dist/, from the current git tag
- .gitea/workflows/build.yml: now pulls the custom image and just
runs `make android`, replacing the ad-hoc Node/SDK install steps
- README.md: describes the pipeline, server, app, and build tooling
- registry.env.example: fix REGISTRY_IMAGE to be fully-qualified
(an unqualified name was silently resolving pushes to Docker Hub
instead of the configured registry)
- docker-compose.yml + tooling-container/src/server.py: serve
preprocess/OCR/extract over an async job API (POST /jobs, GET
/jobs/{id}) instead of manual host-script runs per receipt
- android/: Kotlin/Compose app - capture a receipt photo, poll job
progress, review/edit extracted fields, save locally (Room), export
to CSV/ODS
- .gitea/workflows/build.yml: build the debug APK and publish it to
dl.ladkau.de on push
- build-image.sh: also pull ollama/ollama so all pipeline images are
ready after one script
- add project logo (also used for the app's launcher icon/splash)
ml