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.
A multi-stage kaniko build replaces / with the last stage's root filesystem,
which deletes $HOME/.docker/config.json. Kaniko then resolves credentials at
push time without them, asks the registry for an anonymous token and Gitea
rejects the upload with 401 reqPackageAccess.
Keep the Docker credential store in /kaniko/.docker for the whole image job via
DOCKER_CONFIG and let docker login write there directly. Restore the image job
and document that CI publishes images again.
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.
Alpine/musl cannot load sqlite-jdbc's bundled native library, so the
container failed at startup. Switch the runtime image to
eclipse-temurin:21-jre-jammy and verify the image end-to-end, including
transcoding, against a read-only root filesystem.
The smoke fixture now uses a 192 kbps source so the maxBitRate check
actually proves transcoding instead of direct play.
- FfmpegTranscoder with maxBitRate, format fallback to MP3 and timeOffset
- direct play when no transcode is required, preserving HTTP Range support
- transcoded responses are chunked audio/mpeg with process cleanup
- unit tests for policy and real ffmpeg output
- smoke test covers maxBitRate, timeOffset and format fallback
Clients that use the formPost extension (Feishin, Symfonium) send requests
as application/x-www-form-urlencoded POSTs, not only GET. Register both
methods for every route and cover it in the smoke test.
- getMusicDirectory for folder/album browsing
- server-side play queues with savePlayQueue/getPlayQueue and index variants
- jukebox status and internet radio compatibility responses
- scripts/smoke.sh generates a tagged MP3 library, runs the server and
verifies all endpoints clients use, including Range, download and covers