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

adding scheduled view in torrents tab
Build and Deploy (internal) / Build Transmission Manager Image (push) Successful in 3m22s
Details
Build and Deploy (internal) / Deploy Transmission Manager (internal) (push) Successful in 3s
Details

Browse Source
This commit is contained in:
ivanch
2026-09-25 20:57:09 -03:00
parent 0d686847f2
commit 19c3ee2e26
5 changed files with 141 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
project-context.md
+2 -2
View File
@@ -24,7 +24,7 @@ The app is intentionally small: one Go binary serves both the API and embedded f
- `main.go`: backend entrypoint. Owns the HTTP server, embedded static file serving, environment-driven Transmission RPC client configuration, session-ID handshake, connection warning page, JSON helpers, and API routes.
- `scheduler.go`: SQLite persistence, background scheduling loop, Transmission seed-slot reconciliation, and scheduler API routes.
- `web/index.html`: SPA shell. Defines the header, stats pills, alternative-speed controls, filter input, sort buttons, list container, empty state, error state, footer, and script/style links.
- `web/index.html`: SPA shell. Defines the header, stats pills, alternative-speed controls, torrent search and Scheduled filter, sort buttons, list container, empty state, error state, footer, and script/style links.
- `web/icon.svg`: editable vector source for the app icon.
- `web/icon.png`: reusable raster app icon used by the SPA header and browser tab.
- `web/app.js`: frontend application logic. Owns state, polling, fetch helpers, formatting, session-limit presentation and alternative-speed toggling, torrent classification, sorting, keyed DOM reconciliation, pause/resume actions, and event wiring.
@@ -83,7 +83,7 @@ The scheduler checks every 30 seconds independently of the browser. Its active-s
## Frontend Architecture
The frontend is a single page with module-level state in `web/app.js`. It polls on a user-selectable interval, defaults to 3 seconds, and fetches torrents, stats, and session settings in parallel. The Torrents and Scheduler views are accessible tabs. The Scheduler view fetches its state every 10 seconds while visible and loads history when it changes.
The frontend is a single page with module-level state in `web/app.js`. It polls on a user-selectable interval, defaults to 3 seconds, and fetches torrents, stats, and session settings in parallel. The Torrents and Scheduler views are accessible tabs. Scheduler state is fetched every 10 seconds while the page is visible so the Torrents view can show opt-in badges, filter to scheduled torrents, and change opt-ins on cards. The Scheduler view loads history when it changes.
Important patterns: