mirror of https://github.com/kikootwo/ReadMeABook.git synced 2026-06-03 04:40:09 +00:00

Files

T

Claude a3381cba31 Fix qBittorrent service not reloading config after settings change

Root cause: Singleton caching issue
The qBittorrent service uses a singleton pattern with a configLoaded flag.
Once initialized, it NEVER re-reads the database config, even when the
user changes settings via the admin settings page.

Flow showing the bug:
1. Wizard saves download_dir to database ✓
2. First torrent: service reads config, creates singleton, sets configLoaded=true ✓
3. User changes download_dir in settings page ✓ (database updated)
4. Next torrent: getQBittorrentService() returns CACHED singleton ✗
5. Cached singleton has OLD download_dir value in this.defaultSavePath ✗
6. Category check shows "already has correct save path: /old/path" ✗
7. Download goes to wrong location ✗

The singleton check (line 745):
  if (!qbittorrentService || !configLoaded) {
    // Only runs if service doesn't exist or config failed
  }
Once both exist, this block is SKIPPED forever!

Fix:
1. Added invalidateQBittorrentService() function
   - Resets qbittorrentService = null
   - Resets configLoaded = false
   - Forces reload from database on next use

2. Call invalidation from settings APIs:
   - After updating paths (download_dir, media_dir)
   - After updating download client (URL, credentials)

3. Next torrent addition:
   - getQBittorrentService() sees null singleton
   - Re-reads config from database
   - Creates new service with current download_dir
   - Category updated with correct path

Benefits:
- Settings changes take effect immediately
- No app restart needed
- Category save path always matches current config
- Download client credentials always current

Updated documentation to explain singleton invalidation pattern.

2026-01-28 11:41:57 -05:00

README.md

ReadMeABook - Audiobook Library Management

Status: MVP Complete (Phases 1-4 ✅) | Docker deployment pending

Stack

Frontend: Next.js 14+, TypeScript, Tailwind CSS
Backend: Node.js/Express via Next.js API routes
Database: PostgreSQL (Docker embedded)
Queue: Bull + Redis (Docker embedded)
Deployment: Single Docker image

Architecture

Docker Container
├── Next.js App (Frontend + Backend)
├── PostgreSQL (users, audiobooks, requests, config, jobs)
├── Bull Queue + Redis (background jobs)
└── Volumes: /config, /downloads, /media

External integrations: Plex (auth + library), Prowlarr/Jackett (indexers), qBittorrent/Transmission (downloads), Audible (metadata scraping)

Core Features (Implemented)

Plex OAuth authentication
Setup wizard (8 steps: admin, Plex, Prowlarr, download client, paths)
Audiobook discovery (popular, new releases via Audible scraping)
Request management with status tracking
Automation pipeline: search → download → organize → Plex scan
Admin dashboard with metrics, active downloads, recent requests
Settings pages (Plex, Prowlarr, download client, paths)
Scheduled jobs (Plex scan, Audible refresh, retry logic, cleanup)
User/admin RBAC

User Flow

Login with Plex → 2. Search/browse audiobooks → 3. Request → 4. Auto: search indexers → download torrent → organize files → scan Plex → 5. Available in Plex library

Documentation Map

Backend:

database.md - PostgreSQL schema, Prisma ORM
services/auth.md - Plex OAuth, JWT sessions
services/config.md - Settings storage, encryption
services/jobs.md - Bull queue, background processors
services/scheduler.md - Recurring jobs (cron)

Integrations:

integrations/plex.md - Library scanning, OAuth, matching
integrations/audible.md - Web scraping, metadata

Automation (Phase 3):

phase3/README.md - Automation pipeline overview
phase3/qbittorrent.md - Download client integration
phase3/prowlarr.md - Indexer search
phase3/ranking-algorithm.md - Torrent selection
phase3/file-organization.md - File management, seeding

Frontend:

frontend/components.md - React components catalog
frontend/routing-auth.md - Route protection, auth flow
frontend/pages/login.md - Login page design

Admin:

admin-dashboard.md - Metrics, monitoring
settings-pages.md - Configuration UI
setup-wizard.md - First-time setup flow

Deployment:

deployment/docker.md - Docker Compose, volumes, env vars

Development Phases

✅ Phase 1: Foundation (auth, database, setup wizard) ✅ Phase 2: User features (discovery, requests, dashboard) ✅ Phase 3: Automation (search, download, organize, Plex integration) ✅ Phase 4: Admin tools (dashboard, settings, monitoring, scheduled jobs) ⏳ Phase 5: Enhanced features (WebSockets, advanced search) ⏳ Phase 6: Advanced admin (analytics, notifications, quality profiles)

Standards

Files ≤400 lines
File headers link to documentation
Update docs before/after code changes
Type-safe TypeScript throughout
Encrypted sensitive config (AES-256)