# Transmission

Your torrent daemon, driven from Officer.

Transmission does not install or supervise the daemon and holds no torrents of its own. You point it at a
daemon's RPC endpoint; it speaks that protocol for you and keeps the credentials server-side, so no
device ever carries them.

## What you get

- **The queue**, virtualised — thousands of torrents scroll without the list breaking a sweat.
- **Per-torrent detail**: general, files (with per-file priority and wanted/unwanted), peers, trackers.
- **The usual verbs** — add by magnet or file, remove with or without data, move, relabel, set options.
- **Stats and speed limits**, including the alternative-speed schedule.

## What you need

**A Transmission daemon you already run**, with RPC enabled — its URL, the RPC path (usually
`/transmission/rpc`), and a username and password if it requires them.

Nothing else. No system packages, no host binaries.

## Setup

1. Install the plugin.
2. Open **/transmission → Connection** and enter the daemon's address and credentials.
3. It probes the RPC endpoint and stores the connection encrypted, server-side.

## Worth knowing

- **The connection is stored in a core table, not this plugin's.** `service_connections` is the app
  store's shared credential store, keyed by account and service. This plugin ships no schema of its own —
  see PLUGIN.md for why that is deliberate and what it costs.
- **It polls.** A torrent client's whole value is live numbers, so the panels refresh on a timer while
  open. That is a real difference from, say, a bookkeeping app, and it is intentional.
- **It is a client, not a supervisor.** If the daemon stops, this reports that it cannot reach it. It
  will not start it for you.