Is this a new feature request?
Wanted change
Compile Tvheadend with the new Vue-based web GUI enabled, so it's available alongside (or eventually replacing) the classic ExtJS interface, matching what upstream Tvheadend now ships by default for builds after July 8, 2026.
Currently the Dockerfile's ./configure call has no --enable-vue_build or --enable-vue_cache flag, and the buildstage doesn't install nodejs/npm, so the image compiles without the Vue frontend regardless of how recent the checked-out TVHEADEND_COMMIT is.
Reason for change
Upstream Tvheadend replaced the long-obsolete ExtJS frontend with a new Vue/NodeJS-based GUI as the default for the project going forward (announcement: https://tvheadend.org/d/9453-tvheadend-web-gui/1). The classic GUI is only being kept temporarily while the new one stabilizes. Right now this image can't produce the new interface at all, so anyone pulling lscr.io/linuxserver/tvheadend:latest is stuck on the old UI with no path to the new one, and will eventually be stuck when Classic is removed upstream.
Proposed code change
In Dockerfile, buildstage:
Reference from a user who confirmed this works for a manual build:
AUTOBUILD_CONFIGURE_OPTIONS="--enable-vue_build" sudo ./Autobuild.sh -t <target>
Once upstream populates the pcloud_cache/vue_cache prebuilt assets, --enable-vue_cache could be used instead to avoid the npm build cost in CI.
Is this a new feature request?
Wanted change
Compile Tvheadend with the new Vue-based web GUI enabled, so it's available alongside (or eventually replacing) the classic ExtJS interface, matching what upstream Tvheadend now ships by default for builds after July 8, 2026.
Currently the Dockerfile's ./configure call has no --enable-vue_build or --enable-vue_cache flag, and the buildstage doesn't install nodejs/npm, so the image compiles without the Vue frontend regardless of how recent the checked-out TVHEADEND_COMMIT is.
Reason for change
Upstream Tvheadend replaced the long-obsolete ExtJS frontend with a new Vue/NodeJS-based GUI as the default for the project going forward (announcement: https://tvheadend.org/d/9453-tvheadend-web-gui/1). The classic GUI is only being kept temporarily while the new one stabilizes. Right now this image can't produce the new interface at all, so anyone pulling lscr.io/linuxserver/tvheadend:latest is stuck on the old UI with no path to the new one, and will eventually be stuck when Classic is removed upstream.
Proposed code change
In Dockerfile, buildstage:
Reference from a user who confirmed this works for a manual build:
AUTOBUILD_CONFIGURE_OPTIONS="--enable-vue_build" sudo ./Autobuild.sh -t <target>Once upstream populates the pcloud_cache/vue_cache prebuilt assets, --enable-vue_cache could be used instead to avoid the npm build cost in CI.