The Gitea registry rejects kaniko pushes from job containers with
401 reqPackageAccess even though the same credentials work from a normal
machine, so the image job could never go green.
Drop the image job; CI now only runs unit tests, the smoke test and the
Helm chart lint. Add scripts/release.sh, which builds and pushes the
image from a trusted machine and can optionally apply the users secret
and run helm upgrade.
The runner does not expose its Docker socket to job containers, so the
image job could not run docker build. Include the kaniko executor in the
CI image and build/push directly from the job; docker login only writes
the registry credentials file.
Bump the CI image tag to 2.
Add ci/Dockerfile (JDK 21, Gradle 8.14.3, ffmpeg, sqlite3, node,
docker CLI and Helm) and build it as taptap/audiomanager-ci. Workflows
now start from that image instead of downloading a JDK and installing
packages on every run.
The registry namespace is the lowercased package owner `taptap`, not
`tap-tap`; update the chart, workflow and documentation accordingly.
The image build uses plain docker build/push, since the job container
starts with no buildx plugin.
- multi-stage Dockerfile with ffmpeg on Alpine JRE 21
- Helm chart for k3s: library ConfigMap, Vault users secret, data PVC,
read-only hostPath media, ingress, probes and security context
- Gitea Actions runs tests, smoke test and chart lint, then builds and
pushes the image on main and version tags