ivanch/transmission-manager
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

adding scheduler slots
Build and Deploy (internal) / Build Transmission Manager Image (push) Successful in 2m20s
Details
Build and Deploy (internal) / Deploy Transmission Manager (internal) (push) Successful in 3s
Details

Browse Source
This commit is contained in:
ivanch
2026-09-23 18:32:32 -03:00
parent c98af34202
commit 0d686847f2
5 changed files with 37 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
project-context.md
+2 -2
View File
@@ -6,7 +6,7 @@ This file is the canonical project context for AI agents working on Transmission
Transmission Manager is a lightweight local/LAN web app for viewing and managing torrents from a Transmission RPC daemon. The product goal is a fast, clean, dark-mode SPA that feels modern while remaining simple to build, deploy, and inspect.
The app is intentionally small: one Go binary serves both the API and embedded frontend assets. The frontend is vanilla JavaScript, HTML, and CSS, with no package manager, no compile step, and no JS framework. A server-side scheduler rotates opted-in completed torrents through a limited number of seed slots and records cycle history.
The app is intentionally small: one Go binary serves both the API and embedded frontend assets. The frontend is vanilla JavaScript, HTML, and CSS, with no package manager, no compile step, and no JS framework. A server-side scheduler rotates opted-in completed torrents through a configurable number of active slots and records cycle history.
## Technology Stack
@@ -79,7 +79,7 @@ Alternative-speed controls use the effective profile: alternative caps when `alt
The scheduler uses torrent hashes because Transmission numeric IDs can change after a daemon restart. It makes a lightweight `torrent-get` request for `hashString`, `name`, `percentDone`, `status`, `uploadedEver`, and `error`. It uses `torrent-start-now` for managed slots and `torrent-stop` for rotation; ordinary manual Resume keeps using `torrent-start`. Only opted-in, complete, error-free torrents are eligible. Manual actions on opted-in torrents are temporary; the next scheduler check restores the selected slot allocation.
The scheduler checks every 30 seconds independently of the browser. It defaults to one slot, allows 1–100, and only limits opted-in torrents. Each active slot tracks the last increase in `uploadedEver`; one hour without an increase makes it eligible to rotate to the least recently seeded waiting torrent. With no waiting torrent, the active one stays. A continuously uploading torrent may retain its slot indefinitely. SQLite retains settings, opt-ins, slot timestamps, and all cycle events across restarts; history is paged 50 events at a time.
The scheduler checks every 30 seconds independently of the browser. Its active-slot setting defaults to one and allows 1–100. Only opted-in completed torrents consume these slots or receive scheduler start/stop actions; unopted torrents retain their Transmission state, including in-progress downloads and seeds. Each active slot tracks the last increase in `uploadedEver`; one hour without an increase makes it eligible to rotate to the least recently seeded waiting torrent. With no waiting torrent, the active one stays. A continuously uploading torrent may retain its slot indefinitely. SQLite retains settings, opt-ins, slot timestamps, and all cycle events across restarts; history is paged 50 events at a time.
## Frontend Architecture