Skip to content

Latest commit

 

History

History
20 lines (14 loc) · 1.46 KB

Developing-alternate-WebUIs-(WIP).md

File metadata and controls

20 lines (14 loc) · 1.46 KB
Raw

WIP

From qBittorrent v4.1.0 and on, the WebUI architecture was expanded to allow the use of alternate set of HTML files, allowing customization of the WebUI separated from the evolution of the core qBittorrent code.

Also, this mechanism is controlled via configuration options (core UI preferences window or config file), and the WebUI files (html, css, js, ...) are external to the program so it's easier than ever to test and modify the WebUI's functionality, look and feel without need of rebuilding the executable.

Public and Private WebUI files separation

In order to increase security, a public (login process handling) and private (WebUI functionality) separation of files is implemented (see core WebUI files' segregation as ref: https://github.com/qbittorrent/qBittorrent/tree/master/src/webui/www)

First steps to an alternate WebUI:

Copy the files: https://github.com/qbittorrent/qBittorrent/tree/master/src/webui/www to a <new folder> https://github.com/qbittorrent/qBittorrent/tree/master/src/icons to <new folder>/public https://github.com/qbittorrent/qBittorrent/tree/master/src/icons to <new folder>/private

Enable AltWebUI on the options and point the entry WebUI\RootFolder to <new folder>, then launch qBittorrent. Access the WebUI as always, modify the files at <new folder> according to your needs and refresh the browser to see the changes reflected.

References: