Forge Home


Installs and configures the headless component of the Transmission BitTorrent client.


6,029 latest version

4.3 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 2.2.1 (latest)
  • 2.2.0
  • 2.1.0
  • 2.0.0
  • 1.2.1
  • 1.2.0 (deleted)
  • 1.1.4
  • 1.1.3
  • 1.1.2
  • 1.1.1
  • 1.1.0
  • 1.0.0
released Mar 20th 2018
This version is compatible with:
  • Puppet Enterprise 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >=4.6.1 <5.0.0

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'CraigWatson1987-transmission', '2.2.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add CraigWatson1987-transmission
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install CraigWatson1987-transmission --version 2.2.1

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



CraigWatson1987/transmission — version 2.2.1 Mar 20th 2018


Build Status Puppet Forge

Table of Contents

  1. Overview - What is the puppet-transmission module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with puppet-transmission
  4. Usage - Configuration options and additional functionality
  5. Reference - An under-the-hood peek at what the module is doing
  6. Limitations - OS compatibility, etc.
  7. Development - Guide for contributing to the module


This Puppet module installs and configures the transmission daemon - the headless component of the Transmission BitTorrent client.

Puppet 3 Support

Please note that the master branch of this module does not support Puppet 3!

On 31st December 2016, support for Puppet 3.x was withdrawn. As such, this module no longer supports Puppet 3, and is actively being migrated to Puppet 4 syntax.

If you require Puppet 3 compatibility, please use version 1.2.1 from the Puppet Forge, or the puppet3 branch in Git.

Module Description

  • Adds the Transmission PPA from ppa:transmissionbt/ppa
  • Installs transmission-cli,transmission-common and transmission-daemon packages
  • Downloads and periodically updates blocklists if configured
  • Configures the configuration file for Transmission at /etc/transmission-daemon/settings.json
  • Enables and starts the transmission-daemon daemon/service


Beginning With puppet-transmission

To accept default class parameters (correct in most situations):

include transmission

Usage Example

To specify an RPC user/password, set a custom port number for RPC and peer connections and enable mandatory encryption for peer connections:

class { 'transmission':
  rpc_username => 'rpcuser',
  rpc_password => 'somecomplexpasswordgoeshere',
  rpc_port     => 8080,
  peer_port    => 54612,
  encryption   => 2,


Transmission Configuration Parameters



  • Places the daemon configuration and service defaults files
  • Configures the blocklist update cron, if enabled


  • Adds the Transmission Apt PPA to the system
  • Installs the packages necessary to run the headless daemon


  • Ensures the transmission-daemon service is running
  • Copies the temporary daemon settings file on-change by stopping and starting the daemon


  • The module does not manage or install the transmission-gtk package for the client's GUI

Supported Operating Systems

  • Ubuntu (tested on 14.04 LTS)


  • Copyright (C) Craig Watson -
  • Distributed under the terms of the Apache License v2.0 - see LICENSE file for details.
  • Further contributions and testing reports are extremely welcome - please submit a pull request or issue on GitHub