Skip to content

0021. Alternate Web Frontend Deployment

  • Status: accepted
  • Date: 2026-05-30
  • Deciders: lusoris
  • Related: PR #696

Context

New web frontend deployment for Jellyfin using Vue.js

Decision

Deploy alternate web frontend at jf.media.cauda.dev with a static SPA pointing to the existing in-cluster backend.

Alternatives considered

  • Replace the stock Jellyfin web UI in place — rejected: keeps the official UI as the stable default and lets the Vue SPA iterate independently without risking the primary media interface.
  • Host the SPA outside the cluster — rejected: it targets the in-cluster Jellyfin backend and shares the same auth/gateway path, so co-locating it behind the existing Gateway is simpler than a separate origin.

Consequences

  • A second, independent frontend at jf.media.cauda.dev against the same Jellyfin backend; users can pick either UI.
  • The SPA is a static build (apps/media/jellyfin-vue/), so it adds negligible runtime cost and introduces no new backend.

References

  • PR #696 — feat(jellyfin-vue): deploy alternate web frontend at jf.media.cauda.dev