Transmission: Difference between revisions
imported>Dywedir m Update link |
imported>Fufexan m Add page to Applications category |
||
| 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. | ||
[[Category: Applications]] | |||
Revision as of 20:09, 9 August 2022
 |
This article or section needs expansion.
Reason: This article is a stub. (Discuss in Talk:Transmission#)
Please consult the pedia article metapage for guidelines on contributing. |
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.