WebUI Vue
The Vue-based WebUI lives in webui-vue/. It was introduced as a
technical preview in Bareos 25.1 and is the default WebUI in Bareos 26.
The classic PHP-based WebUI in webui/ remains available in parallel.
Coexistence model
The repository currently contains two different WebUI implementations:
webui/for the classic PHP-based WebUIwebui-vue/for the Vue-based WebUI
Documentation, packaging, and operational guidance should reflect that both variants currently coexist. Changes to the Vue WebUI should not implicitly assume that it has already replaced the classic WebUI everywhere.
Repository layout
The most relevant parts of the Vue WebUI are:
webui-vue/src/for the application sourcewebui-vue/src/pages/for page-level route componentswebui-vue/src/components/for reusable UI componentswebui-vue/src/composables/for shared page and data-loading logicwebui-vue/src/stores/for Pinia storeswebui-vue/src/generated/for generated version and translation datawebui-vue/tests/unit/for unit testswebui-vue/tests/e2e/for Playwright-based end-to-end tests
Build and installation
The installable SPA bundle is generated from the repository root with:
cmake --build <builddir> --target bareos-webui-vue-build
The build logic is implemented in:
webui-vue/CMakeLists.txtwebui-vue/build-dist.cmake
The Vue package is bareos-webui-vue, which provides
bareos-webui. The PHP package is bareos-webui-php.
The installed Apache configuration is generated from:
webui-vue/install/apache/bareos-webui-vue.conf.in
The SPA is installed below
$CMAKE_INSTALL_FULL_DATAROOTDIR/bareos-webui-vue
(normally /usr/share/bareos-webui-vue/) and exposed at /bareos/.
The root URL and the former /bareos-webui-new/ technical-preview URL
redirect to /bareos/; the PHP URL remains /bareos-webui.
Runtime architecture
Unlike the classic PHP WebUI, the Vue WebUI does not talk to the Director through PHP. Instead it uses bareos-webui-proxy for both HTTP session handling and WebSocket-based director communication.
The default Apache configuration:
serves the SPA from
/bareos/rewrites SPA routes back to
index.htmlproxies
/bareos/wsto bareos-webui-proxy on port 9104proxies
/bareos/api/to bareos-webui-proxy on port 9104
Apache removes the /bareos prefix when forwarding to the proxy.
The browser uses /bareos/api/session,
/bareos/api/session/login, and /bareos/api/session/logout.
The proxy itself provides the endpoints
/api/session, /api/session/login, and
/api/session/logout.
The WebSocket side is then used for the live director connection once the
session has been established.
The proxy configuration behavior is:
without
--config, it first tries/etc/bareos-webui-proxy/bareos-webui-proxy.iniif that file is missing, it uses built-in defaults
with explicit
--config, the specified file is required
The default configuration template is installed as
bareos-webui-proxy.ini in $configtemplatedir.
Testing
Typical local validation commands are:
cd webui-vue && npm run build
cd webui-vue && npm run test:unit
ctest --test-dir cmake-build --parallel "$(nproc)" --output-on-failure -R '^webui-vue:'
The browser-based system tests use the shared WebUI Vue test setup under:
systemtests/tests/webui-vue-common/
Translations
The Vue WebUI currently reuses the legacy WebUI locale sources and generated catalog data.
Relevant files are:
webui-vue/scripts/generate-webui-i18n.mjswebui-vue/src/generated/webui-locales.jswebui-vue/src/generated/webui-messages.jswebui/module/Application/language/
To regenerate the committed Vue translation catalog files, run:
cd webui-vue && npm run generate:i18n
Documentation guidance
When documenting Vue WebUI work:
add operator-facing documentation to the introduction/tutorial manual
add implementation and workflow details here in the developer guide
distinguish the Bareos 25.1 technical preview from the default Vue WebUI in Bareos 26
avoid wording that implies the classic WebUI no longer exists unless that product decision has changed