Smart Space Management#

Disk space is one of the biggest headaches when seeding. AniBT-Speed implements an intelligent deletion strategy based on time and share ratio:

1
Space alert threshold: 85% (triggers cleanup)
2
Protection window: 8 hours (new torrents are protected)
3
Boundary time: 12 hours
4

5
Deletion priority:
6
  - Under 8h   → Force protect, never delete
7
  - 8h ~ 12h   → Delete high ratio first (already contributed enough)
8
  - Over 12h   → Delete low ratio first (nobody wants it)

The core logic: new torrents need protection, mid-age torrents with high ratios have already contributed enough, and old torrents with low ratios are unwanted and can be cleaned up.

RSS Feeds with Load Balancing#

When you have multiple qBittorrent instances, which one should handle a new torrent? AniBT-Speed uses a load balancing algorithm:

1
score = active_torrents * 1.0 + upload_speed_mbps * 0.3 + paused_torrents * 0.2
2
# Lower score = lighter load = preferred for new tasks

RSS feeds support two modes:

• Auto-assign (instance_id = 0): Backend polls RSS and selects the best instance via load balancing
• Fixed instance (instance_id > 0): Uses qBittorrent’s native RSS rules, bound to a specific instance

Smart Queue Management#

When a torrent has zero leechers across all trackers and DHT, continuing to seed wastes resources. The queue manager automatically pauses these torrents and resumes them when new leechers appear.

Rate Limiting#

To avoid impacting other services on the server, rate limiting has two tiers:

Sliding window limits are also supported: set hourly or daily traffic caps, and speeds are automatically reduced when exceeded.

Anti-Leeching Protection#

Integrated PeerBanHelper automatically bans peers using leeching clients. Supports BTN cloud rules and Thunder client restrictions.

Telegram Notifications#

All key events can be pushed to Telegram:

• Torrent download completed
• Torrent deleted (with reason)
• Space alerts
• Daily summary (customizable push time)

Yaml File#

1
services:
2
  backend:
3
    image: ghcr.io/yuri-nagasaki/anibt-speed-backend:latest
4
    container_name: anibt-speed-backend
5
    environment:
6
      - SECRET_KEY=${SECRET_KEY:-change-me}
7
      - ADMIN_PASSWORD=${ADMIN_PASSWORD:-admin}
8
      - TZ=Asia/Shanghai
9
    volumes:
10
      - ./backend/data:/app/data
11
    networks:
12
      - anibt
13
    restart: unless-stopped
14

15
  frontend:
16
    image: ghcr.io/yuri-nagasaki/anibt-speed-frontend:latest
17
    container_name: anibt-speed-frontend
18
    ports:
19
      - "127.0.0.1:6868:6868"
20
    depends_on:
21
      - backend
22
    networks:
23
      - anibt
24
    restart: unless-stopped
25

26
  peerbanhelper:
27
    image: ghostchu/peerbanhelper:latest
28
    container_name: anibt-speed-pbh
29
    environment:
30
      - TZ=Asia/Shanghai
31
    ports:
32
      - "127.0.0.1:9898:9898"
33
    volumes:
34
      - ./peerbanhelper/data:/app/data
35
    networks:
36
      - anibt
37
    restart: unless-stopped
38

39
networks:
40
  anibt:
41
    driver: bridge

Prerequisites#

• Docker + Docker Compose
• Git
• One or more running qBittorrent instances

One-Click Deployment#

1
# Clone the repository
2
git clone https://github.com/Yuri-NagaSaki/AniBT-Speed.git
3
cd AniBT-Speed
4

5
# Deploy (pulls pre-built images from GHCR)
6
chmod +x deploy.sh
7
./deploy.sh

The deployment script automatically:

1. Checks for Docker and other dependencies
2. Generates a .env file with a random SECRET_KEY
3. Pulls images and starts all services
4. Verifies all services are running

TIP

To build images locally instead, use BUILD_LOCAL=1 ./deploy.sh

Initial Configuration#

After deployment:

1. Open http://your-server-ip:6868 and log in with the password from .env
2. Go to “Instances” and add your qBittorrent instance(s)
3. Go to “RSS Manager” and add RSS feed subscriptions
4. (Optional) Configure Telegram notifications
5. (Optional) Visit http://127.0.0.1:9898 to configure PeerBanHelper

Health Check#

The project includes a 26-item health check script:

1
chmod +x test.sh
2
./test.sh

Checks cover container status, network isolation, API endpoints, port exposure, internal connectivity, timezone configuration, and data persistence.