Use the CI-published :latest tag with pullPolicy Always, since the chart
previously defaulted to appVersion 0.1.0, which is not published as an image.
Add ingress annotations with a cert-manager ClusterIssuer so the TLS secret is
issued instead of having to exist beforehand.
Extend release.sh --deploy to create the registry image pull secret from the
local Docker config and pass it to the release, and document both the scripted
and manual deployment paths.
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