unkinben
9f8d9014d3
Why: - The build should pull from our own source fork so local HA patches can be carried and pinned, rather than cloning the upstream GitHub tree directly. How: - Point the clone URL in the Makefile and both Woodpecker pipelines at https://git.unkin.net/unkin/jellyfin-ha-src.git. - Keep UPSTREAM_REF at d4f9c12c22d3a640f3b0a3622b23b8cd01d044ad, which is the seeded fork main, so the produced image is byte-identical for now; the feature bump is a later change.
jellyfin-ha (container build)
Build-orchestration repo for ZoltyMat/jellyfin-ha — a Jellyfin fork that adds distributed, Redis-backed transcoding for multi-pod Kubernetes (lease-aware cleanup, HA session takeover, optional PostgreSQL).
This repo does not vendor the fork's source. It pins an upstream commit, builds the .NET 10 server, and produces a runtime container image pushed to the Gitea registry.
What it produces
artifactapi.k8s.syd1.au.unkin.net/docker-internal/jellyfin-ha:<tag> — an mcr.microsoft.com/dotnet/aspnet:10.0 based image with ffmpeg and
the prebuilt jellyfin-web client, running the published jellyfin-ha server.
Layout
| File | Purpose |
|---|---|
UPSTREAM_REF |
Pinned upstream commit SHA. Bumping the fork = edit this + cut a release. |
Dockerfile.runtime |
Runtime-only image; COPYs the CI-produced publish-output/ and the web client. |
Makefile |
Local make publish / make build; make patch|minor|major to tag + push a release. |
.woodpecker/build.yaml |
PR pipeline: dotnet publish + docker dry_run. |
.woodpecker/docker.yaml |
Tag (v*) pipeline: dotnet publish + build & push to the Gitea registry. |
Releasing
- To track a newer upstream, update
UPSTREAM_REFto the desired commit SHA and merge via PR. - Cut a release:
make patch(orminor/major) tagsvX.Y.Zand pushes it, which triggers.woodpecker/docker.yamlto build and pushartifactapi.k8s.syd1.au.unkin.net/docker-internal/jellyfin-ha:vX.Y.Z+:latest.
Local build
make build # clones pinned upstream, dotnet publish, docker build
Requires the .NET 10 SDK and Docker. make publish runs just the clone + publish into ./publish-output.
Deployment
Deployed to Kubernetes via ArgoCD — see argocd-apps (apps/base/jellyfin, media ApplicationSet/project).