qbit_manage/web-ui
bobokun 5a4ddf0112
4.6.0 (#931)
# Requirements Updated
- "humanize==4.13.0"
- "ruff==0.12.11"

# Breaking Changes
- **DEPRECATE `QBT_CONFIG` / `--config-file` OPTION**
- No longer supporting `QBT_CONFIG` / `--config-file`. Instead please
switch over to **`QBT_CONFIG_DIR` / `--config-dir`**.
- `QBT_CONFIG` / `--config-file` option will still work for now but is
now considered legacy and will be removed in a future release.
- **Note**: All yml/yaml files will be treated as valid configuration
files and loaded in the `QBT_CONFIG_DIR` path. Please ensure you
**remove** any old/unused configurations that you don't want to be
loaded prior to using this path.

# Improvements
- Adds docker support for PUID/PGID environment variables
- Dockerfile copies the latest `config.yml.sample` in the config folder
- Add `QBT_HOST` / `--host` option to specify webUI host address (#929
Thanks to @QuixThe2nd)
- WebUI: Quick action settings persist now

# Bug Fixes
- WebUI: Fix loading spinner to be centered in the webUI

**Full Changelog**:
https://github.com/StuffAnThings/qbit_manage/compare/v4.5.5...v4.6.0

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Fabricio Silva <hi@fabricio.dev>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Parsa Yazdani <parsa@yazdani.au>
Co-authored-by: Actionbot <actions@github.com>
2025-08-30 14:54:13 -04:00
..
css 4.6.0 (#931) 2025-08-30 14:54:13 -04:00
img 4.5.4 (#910) 2025-08-16 22:28:26 -04:00
js 4.6.0 (#931) 2025-08-30 14:54:13 -04:00
index.html 4.5.5 (#922) 2025-08-24 18:44:54 -04:00
README.md v4.5.0 (#862) 2025-07-11 19:13:41 -04:00

qBit Manage Web UI

Overview

The qBit Manage Web UI provides a modern interface for configuring and managing qBit Manage. It offers real-time editing of YAML configuration files through an intuitive visual interface, eliminating the need for manual file editing.

Project Structure

web-ui/
├── css/               # Stylesheets
│   ├── components/    # Component-specific styles
│   ├── main.css       # Global styles
│   ├── responsive.css # Responsive layouts
│   └── themes.css     # Theme definitions
├── img/               # Application images and icons
├── js/                # Application logic
│   ├── api.js         # Backend communication
│   ├── app.js         # Main application
│   ├── components/    # UI components
│   ├── config-schemas/ # Configuration schemas
│   └── utils/         # Helper functions
└── index.html         # Application entry point

Key Features

  • Visual Configuration Editor: Intuitive forms for editing YAML configurations
  • Real-time Validation: Instant feedback on configuration errors
  • Undo/Redo History: Track and revert changes with history management
  • Theme Support: Light/dark mode with system preference detection
  • Responsive Design: Works on desktop and mobile devices
  • YAML Preview: Real-time preview of generated configuration

Configuration Sections

The UI organizes configuration into logical sections:

  1. Commands: Manage script execution workflows
  2. qBittorrent Connection: Configure qBittorrent API access
  3. Settings: Application preferences and behavior
  4. Directory Paths: Define important filesystem locations
  5. Categories: Torrent category management
  6. Category Changes: Bulk category modification rules
  7. Tracker Configuration: Per-tracker settings
  8. No Hard Links: Category-specific hardlink handling
  9. Share Limits: Ratio and seeding time rules
  10. Recycle Bin: Deleted torrent management
  11. Orphaned Files: Cleanup of unregistered files
  12. Notifications: Alert configuration
  13. Logs: View application logs

Technical Architecture

Frontend Components

  • ConfigForm.js: Dynamic form generator based on JSON schemas
  • CommandPanel.js: Interface for executing management commands
  • LogViewer.js: Real-time log display component
  • HistoryManager.js: Undo/Redo functionality implementation

API Integration

The UI communicates with the backend through a RESTful API:

sequenceDiagram
    participant UI as Web UI
    participant API as FastAPI Backend
    participant QBM as qBit Manage

    UI->>API: HTTP Request (GET/POST)
    API->>QBM: Process Configuration
    QBM-->>API: YAML Validation
    API-->>UI: Response with Status

Key API endpoints:

  • GET /api/configs: List available configurations
  • PUT /api/configs/{filename}: Update configuration file
  • POST /api/run-command: Execute management commands
  • GET /api/logs: Stream application logs

Error handling includes:

  • JWT authentication
  • Automatic retry on network failures
  • Websocket support for real-time updates

Usage Notes

  1. Ensure the qBit Manage backend is running
  2. Open index.html in a modern browser
  3. Select a configuration file from the dropdown
  4. Navigate sections using the sidebar
  5. Use the preview button to see generated YAML
  6. Save changes when complete

Keyboard Shortcuts:

  • Ctrl+S: Save current configuration
  • Ctrl+R: Toggle Run Commands modal
  • Ctrl+Z: Undo last change
  • Ctrl+Y: Redo last change
  • Ctrl+/: Toggle Help modal
  • Ctrl+P or Cmd+P: Toggle YAML preview
  • Escape: Close modals/panels