Bareos WebUI Vue

The Vue-based Bareos WebUI is a new single-page application located in webui-vue/. It provides a modern WebUI implementation that coexists with the classic PHP-based Bareos Webui.

Warning

The Vue-based WebUI is currently a technical preview. It is intended for evaluation, early adoption, and iterative development. The classic PHP-based WebUI remains available in parallel and should still be considered the default WebUI for production environments unless the Vue WebUI preview has been explicitly evaluated for the intended use case.

Coexistence with the classic WebUI

The current Bareos documentation distinguishes between two WebUI variants:

  • Bareos Webui documents the classic PHP-based WebUI.

  • This page documents the new Vue-based WebUI technical preview.

The two interfaces are designed to exist in parallel. In a typical Apache deployment they use separate URLs:

  • classic WebUI: /bareos-webui

  • Vue WebUI preview: /bareos-webui-vue

The Vue WebUI uses the same Bareos Director console concepts as the classic WebUI, so user access still depends on properly configured Console (Dir) resources and matching ACLs.

Architecture overview

The Vue WebUI consists of:

  • the static SPA bundle installed below /usr/share/bareos-webui-vue

  • an Apache configuration that exposes the bundle below /bareos-webui-vue

  • the bareos-webui-proxy service, which accepts WebSocket connections and forwards requests to the Bareos Director

The default Apache configuration proxies /ws to bareos-webui-proxy on port 9104.

Installation and access

The exact package layout depends on the target platform. Where packaging support is available, the Vue WebUI is installed separately from the classic PHP WebUI and keeps its own Apache configuration file bareos-webui-vue.conf.

For source builds, the installable bundle is generated with:

cmake --build <builddir> --target bareos-webui-vue-build

After installation, open the preview at:

http://HOSTNAME/bareos-webui-vue

To use it successfully, ensure that:

  • the Vue WebUI bundle is installed

  • the Apache configuration for /bareos-webui-vue is enabled

  • bareos-webui-proxy is installed and running

  • the WebSocket proxy target on port 9104 is reachable from Apache

  • suitable Bareos Director console credentials exist

What is already available

The technical preview already covers important day-to-day workflows, including:

  • login with Bareos console credentials

  • dashboard views

  • job overview and job details

  • restore workflows, including plugin restore options

  • client, fileset, schedule, storage, and volume views

  • Director status and message views

  • a console popup for command execution

  • multi-director capable views where supported by the page

Known differences and current limitations

Compared to the classic PHP WebUI, the Vue WebUI preview should currently be viewed as a parallel implementation under active development.

Important differences are:

  • documentation and operational guidance are still catching up

  • some workflows are intentionally presented differently than in the classic WebUI instead of being a 1:1 port

  • the preview depends on bareos-webui-proxy, which is a separate runtime component

  • the classic WebUI should remain available while the preview is being evaluated

When to use which WebUI

Use the classic PHP WebUI when:

  • you want the long-established, primary WebUI

  • your operations depend on currently documented production procedures

  • you prefer the most conservative choice

Use the Vue WebUI preview when:

  • you want to evaluate the new interface

  • you want to test current preview workflows in parallel with the classic UI

  • you are helping validate the future WebUI direction

For now, the recommended approach is to keep both interfaces available and let users compare them against their operational needs.

Further information

For developer-oriented details, see WebUI Vue.