Transmission: Difference between revisions

From NixOS Wiki
imported>Fufexan
m Add page to Applications category
imported>IgorM
Added example for remote access
Line 17: Line 17:


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]]
[[Category: Applications]]

Revision as of 11:57, 4 October 2023

Service configuration

Changes to the configuration in the interface will not persist when the application is re-launched. services.transmission.settings is reset each time the service restarts.

Attribute set whos[e] fields overwrites fields in settings.json (each time the service starts). String values must be quoted, integer and boolean values must not.

<nixpkgs>/nixos/modules/services/torrent/transmission.nix

To persist changes, edit them, look at the [services.transmission.home]/.config/transmission-daemon/settings.json file generated for the setting keys and their values, and save them to services.transmission.settings

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.

Example: allow remote access

To control the daemon remotely, put the following lines in your /etc/nixos/configuration.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)
    };
  };