Transmission: Difference between revisions
imported>Dywedir m Update link |
→Service configuration: GTK or QT packages are not required for the transmission systemd service. The default package is the CLI daemon. |
||
| (9 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{expansion}} | {{expansion}} | ||
[https://transmissionbt.com/ Transmission] is a lightweight, open-source BitTorrent client for Linux that provides both GUI and command-line interfaces for efficient torrent downloading and seeding. | |||
== Installation == | |||
Install by adding transmission_4-qt or transmission_4-gtk to your packages list | |||
<syntaxHighlight lang=nix> | |||
environment.systemPackages = with pkgs; [ transmission_4-qt ]; | |||
</syntaxHighlight> | |||
<syntaxhighlight lang="nix">environment.systemPackages = with pkgs; [ transmission_4-gtk ];</syntaxhighlight> | |||
Transmission 3 has been deprecated in the 25.05 channel and removed in favor of version 4 in the 25.11 channel onwards. | |||
If you still rely on it, consider making a backup before upgrading to transmission 4. | |||
== Service configuration == | == Service configuration == | ||
The transmission daemon can be enabled declaratively as a <code>systemd</code> service with the settings under <code>services.transmission.settings</code>. [https://search.nixos.org/options?type=packages&query=transmission.settings View the documentation for more info]. | |||
Note that <code>services.transmission.package</code> defaults to: | |||
* <code>transmission_3</code> in the deprecated 25.05 channel | |||
* <code>transmission_4</code> from 25.11 onwards | |||
< | Example: | ||
<syntaxHighlight lang=nix> | |||
services.transmission.settings = { | |||
download-dir = "${config.services.transmission.home}/Downloads"; | |||
}; | |||
</syntaxHighlight> | |||
=== Password-protected RPC === | === Password-protected RPC === | ||
The default method of editing the configuration and restarting the daemon will '''not work''' because of the way the configuration is handled. It is however possible to once set it in clear in the settings, and then copy the generated hash to the setting, removing the in-clear copy from the configuration. | The default method of editing the configuration and restarting the daemon will '''not work''' because of the way the configuration is handled. It is however possible to once set it in clear in the settings, and then copy the generated hash to the setting, removing the in-clear copy from the configuration. | ||
=== Example: allow remote access === | |||
To control the daemon remotely, put the following lines in your <code>/etc/nixos/configuration.nix</code>: | |||
<syntaxhighlight lang=nix> | |||
services.transmission = { | |||
enable = true; #Enable transmission daemon | |||
openRPCPort = true; #Open firewall for RPC | |||
settings = { #Override default settings | |||
rpc-bind-address = "0.0.0.0"; #Bind to own IP | |||
rpc-whitelist = "127.0.0.1,10.0.0.1"; #Whitelist your remote machine (10.0.0.1 in this example) | |||
}; | |||
}; | |||
</syntaxhighlight> | |||
[[Category: Applications]] | |||