Configuration
Config file
transtui reads (and creates, with defaults, if missing) ~/.config/transtui/config.ini (or $XDG_CONFIG_HOME/transtui/config.ini if that environment variable is set):
host = 127.0.0.1
port = 9091
username =
password =
poll_interval_ms = 2000
show_splash = 1| Field | Meaning |
|---|---|
host | Transmission daemon address |
port | RPC port (Transmission's default is 9091) |
username / password | RPC authentication, empty if the daemon doesn't require it |
poll_interval_ms | How often the list auto-refreshes (min. 250 ms) |
show_splash | 1/0 - show the splash screen at startup |
The file is written automatically when you change connection or splash-screen settings in the app (g, see Interface) - you rarely need to edit it by hand.
Session settings cache (cache_* keys)
Whenever you change a daemon-side session setting - download folder, speed limits, alt-speed schedule, ratio limit - transtui also remembers that value in config.ini (as session_cache_set and a set of cache_* keys). This exists because transmission-daemon only writes its own settings.json to disk on a clean shutdown, not immediately when a setting is changed over RPC - if the daemon is later killed uncleanly (crash, power loss, kill -9) before a clean stop happens, it reloads its old settings.json on the next start and silently forgets the change.
transtui checks for this every time it connects (at startup, and each time you open settings): if the daemon's current value doesn't match the cache, it pushes the cached value back and shows a status message like "Restored 1 setting(s) the daemon had reverted". This intentionally wins over changes made through any other RPC client (Transmission's own web UI, transmission-remote, ...) since transtui was last used - if you manage the daemon from multiple tools, keep that in mind. These keys are maintained automatically; there's normally no reason to edit them by hand.
Command-line flags
transtui [-H host] [-P port] [-u user] [-p pass] [-i ms]
transtui --add <magnet|url|file> [-H host] [-P port] [-u user] [-p pass]| Flag | Meaning |
|---|---|
-H, --host <host> | Override host for this run |
-P, --port <port> | Override port |
-u, --user <name> | Override username |
-p, --pass <pass> | Override password |
-i, --interval <ms> | Override poll_interval_ms |
-A, --add <source> | Add a torrent and exit immediately, see Browser Integration |
-h, --help | Show help |
The flags do not overwrite config.ini - they only apply to that run. That makes them good for one-off runs, scripts, or pointing at a different daemon temporarily without changing your usual setup.
Connecting to a remote daemon
transtui -H 192.168.1.10 -P 9091 -u username -p passwordWorks against any Transmission daemon that exposes the RPC, local or over the network - transtui just needs to reach the port. The automatic "no daemon found" help (starting/configuring the daemon for you) only applies to 127.0.0.1/localhost though, for obvious reasons: it can't sudo into another machine. See Daemon: setup & troubleshooting.