Transmission - Revision history

Lavafroth: /* Service configuration */ GTK or QT packages are not required for the transmission systemd service. The default package is the CLI daemon.

2025-12-15T02:57:24Z

Service configuration: GTK or QT packages are not required for the transmission systemd service. The default package is the CLI daemon.

← Older revision		Revision as of 02:57, 15 December 2025
Line 13:		Line 13:

	== Service configuration ==		== Service configuration ==
	~~You~~ can declaratively ~~change~~ the settings ~~via Nix by modifying~~ <code>services.transmission.settings</code>. [https://search.nixos.org/options?type=packages&query=transmission.settings View the documentation for more info]. ~~Like the previous section has said before, you'll have~~ to ~~use~~ the ~~nixpkgs transmission-gtk or transmission-qt for this to work~~.		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:		Example:

Lavafroth: /* Installation */ Removed mentions of transmission 3 due to deprecation and removal in active channels

2025-12-15T02:44:17Z

Installation: Removed mentions of transmission 3 due to deprecation and removal in active channels

← Older revision		Revision as of 02:44, 15 December 2025
Line 9:		Line 9:
	<syntaxhighlight lang="nix">environment.systemPackages = with pkgs; [ transmission_4-gtk ];</syntaxhighlight>		<syntaxhighlight lang="nix">environment.systemPackages = with pkgs; [ transmission_4-gtk ];</syntaxhighlight>

	~~If you want to configure~~ the ~~settings declaratively with within configuration.nix, you will have to instead install transmission-qt or transmission-gtk. Do note that this is using version 3.0~~.~~0 instead~~ of version 4.		Transmission 3 has been deprecated in the 25.05 channel and removed in favor of version 4 in the 25.11 channel onwards.
	~~<syntaxHighlight lang=nix>~~		If you still rely on it, consider making a backup before upgrading to transmission 4.
	~~environment.systemPackages = with pkgs; [~~ transmission~~-qt ];~~
	~~</syntaxHighlight>~~
	~~<syntaxHighlight lang=nix>~~
	~~environment~~.~~systemPackages = with pkgs; [ transmission-gtk ];~~
	~~</syntaxHighlight>~~

	== Service configuration ==		== Service configuration ==

Granddave: Add application introduction

2025-10-26T16:26:14Z

Add application introduction

← Older revision		Revision as of 16:26, 26 October 2025
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 ==		== Installation ==
	Install by adding transmission_4-qt or transmission_4-gtk to your packages list		Install by adding transmission_4-qt or transmission_4-gtk to your packages list
Line 5:		Line 7:
	environment.systemPackages = with pkgs; [ transmission_4-qt ];		environment.systemPackages = with pkgs; [ transmission_4-qt ];
	</syntaxHighlight>		</syntaxHighlight>
	<~~syntaxHighlight~~ lang=nix>		<syntaxhighlight lang="nix">environment.systemPackages = with pkgs; [ transmission_4-gtk ];</syntaxhighlight>
	environment.systemPackages = with pkgs; [ transmission_4-gtk ];
	</~~syntaxHighlight~~>

	If you want to configure the settings declaratively with within configuration.nix, you will have to instead install transmission-qt or transmission-gtk. Do note that this is using version 3.0.0 instead of version 4.		If you want to configure the settings declaratively with within configuration.nix, you will have to instead install transmission-qt or transmission-gtk. Do note that this is using version 3.0.0 instead of version 4.

Pigs: /* Service configuration */Use current channel for search.nixos.org link

2025-05-07T16:51:47Z

Service configuration: Use current channel for search.nixos.org link

← Older revision		Revision as of 16:51, 7 May 2025
Line 18:		Line 18:

	== Service configuration ==		== Service configuration ==
	You can declaratively change the settings via Nix by modifying <code>services.transmission.settings</code>. [https://search.nixos.org/options?~~channel=23.11&from=0&size=50&sort=relevance&~~type=packages&query=transmission.settings View the documentation for more info]. Like the previous section has said before, you'll have to use the nixpkgs transmission-gtk or transmission-qt for this to work.		You can declaratively change the settings via Nix by modifying <code>services.transmission.settings</code>. [https://search.nixos.org/options?type=packages&query=transmission.settings View the documentation for more info]. Like the previous section has said before, you'll have to use the nixpkgs transmission-gtk or transmission-qt for this to work.

	Example:		Example:

imported>Jmarmstrong1207: Modify service configuration section to be easier to understand for newer users. Remove section about losing settings at relaunch, because I believe that has been fixed. It works on my machine

2024-02-28T00:06:13Z

Modify service configuration section to be easier to understand for newer users. Remove section about losing settings at relaunch, because I believe that has been fixed. It works on my machine

← Older revision		Revision as of 00:06, 28 February 2024
Line 7:		Line 7:
	<syntaxHighlight lang=nix>		<syntaxHighlight lang=nix>
	environment.systemPackages = with pkgs; [ transmission_4-gtk ];		environment.systemPackages = with pkgs; [ transmission_4-gtk ];
			</syntaxHighlight>

			If you want to configure the settings declaratively with within configuration.nix, you will have to instead install transmission-qt or transmission-gtk. Do note that this is using version 3.0.0 instead of version 4.
			<syntaxHighlight lang=nix>
			environment.systemPackages = with pkgs; [ transmission-qt ];
			</syntaxHighlight>
			<syntaxHighlight lang=nix>
			environment.systemPackages = with pkgs; [ transmission-gtk ];
	</syntaxHighlight>		</syntaxHighlight>

	== Service configuration ==		== Service configuration ==
	~~{{outdated \| This section was created in 2017 and this workaround may not be needed anymore for changing~~ settings~~. This will stay until final confirmation occurs.}}~~		You can declaratively change the settings via Nix by modifying <code>services.transmission.settings</code>. [https://search.nixos.org/options?channel=23.11&from=0&size=50&sort=relevance&type=packages&query=transmission.settings View the documentation for more info]. Like the previous section has said before, you'll have to use the nixpkgs transmission-gtk or transmission-qt for this to work.

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

	<~~blockquote~~>		Example:
	~~Attribute set whos[e] fields overwrites fields in settings~~.~~json (each~~		<syntaxHighlight lang=nix>
	~~time the service starts)~~. ~~String values must be quoted, integer and~~		services.transmission.settings = {
	~~boolean values must not.~~		download-dir = "${config.services.transmission.home}/Downloads";
	~~</blockquote>~~		};
	~~<cite>[https://github~~.~~com/NixOS/nixpkgs/blob/dd705fb45fd17c078522dedb76ee710ed4d3af4b/nixos/modules/~~services~~/torrent/transmission~~.~~nix#L64:L71 <nixpkgs>/nixos/modules/services/torrent/~~transmission.~~nix]<~~/~~cite>~~

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

	=== Password-protected RPC ===		=== Password-protected RPC ===

imported>Jmarmstrong1207: Change to outdated tag

2024-02-19T12:43:25Z

Change to outdated tag

← Older revision		Revision as of 12:43, 19 February 2024
Line 10:		Line 10:

	== Service configuration ==		== Service configuration ==
	{{~~note~~\| This section was created in 2017 and this workaround may not be needed anymore for changing settings. This will stay until final confirmation occurs.}}		{{outdated \| This section was created in 2017 and this workaround may not be needed anymore for changing settings. This will stay until final confirmation occurs.}}

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

imported>Jmarmstrong1207: Add installation guide

2024-02-19T08:55:03Z

Add installation guide

← Older revision		Revision as of 08:55, 19 February 2024
Line 1:		Line 1:
	{{expansion}}		{{expansion}}
			== 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>

	== Service configuration ==		== Service configuration ==

imported>Jmarmstrong1207: Added note of possible deletion for service config

2024-02-19T08:52:06Z

Added note of possible deletion for service config

← Older revision		Revision as of 08:52, 19 February 2024
Line 2:		Line 2:

	== Service configuration ==		== Service configuration ==
			{{note\| This section was created in 2017 and this workaround may not be needed anymore for changing settings. This will stay until final confirmation occurs.}}

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

imported>IgorM: Added example for remote access

2023-10-04T11:57:17Z

Added example for remote access

← Older revision		Revision as of 11:57, 4 October 2023
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]]

imported>Fufexan: Add page to Applications category

2022-08-09T20:09:15Z

Add page to Applications category

← Older revision		Revision as of 20:09, 9 August 2022
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]]