User Tools

Site Tools


nethserver-transmission

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
nethserver-transmission [2015/05/21 21:28]
stephdl [Usage]
nethserver-transmission [2019/06/05 19:48] (current)
Line 8: Line 8:
     We don't track our users, and our website and forums have no third-party ads or analytics.      We don't track our users, and our website and forums have no third-party ads or analytics. 
  
-Easy.+**Easy**.
  
 Transmission is designed for easy, powerful use. We've set the defaults to "Just Work" and it only takes a few clicks to configure advanced features like watch directories, bad peer blocklists, and the web interface. When Ubuntu chose Transmission as its default BitTorrent client, one of the most-cited reasons was its easy learning curve. Transmission is designed for easy, powerful use. We've set the defaults to "Just Work" and it only takes a few clicks to configure advanced features like watch directories, bad peer blocklists, and the web interface. When Ubuntu chose Transmission as its default BitTorrent client, one of the most-cited reasons was its easy learning curve.
  
 ====Installation==== ====Installation====
-Add my repository +Add my repository, [[nethserver|see how to do it]]
- +
-  yum install http://mirror.de-labrusse.fr/NethServer/6/noarch/nethserver-stephdl-1.0.0-1.ns6.noarch.rpm+
  
 then install the module then install the module
  
-  yum install nethserver-linux-dash --enablerepo=stephdl+  yum install nethserver-transmission --enablerepo=stephdl
  
 after that the transmission-daemon is started, go to https://IP/transmission  after that the transmission-daemon is started, go to https://IP/transmission 
Line 25: Line 23:
  
 ====Usage==== ====Usage====
 +  * Stop the service
 if you want to stop it (enabled/disabled) if you want to stop it (enabled/disabled)
  
Line 30: Line 29:
     signal-event nethserver-transmission-save     signal-event nethserver-transmission-save
  
-Transmission is particular, it doesn't write its configuration on the fly to its settings.json, it does at the shutdown and it reads at the boot time, Therefore when you modify some specific settings as +  * Web application settings 
 +Transmission is particular, it doesn't write its configuration on the fly to its settings.json, **it does at the shutdown and it reads at the boot time**, Therefore when you modify some specific settings **in the web application** of transmission like 
  
   * the rpc-peer (peer port 51413 by default)    * the rpc-peer (peer port 51413 by default) 
Line 37: Line 37:
   * the daemon port (9091 by default)   * the daemon port (9091 by default)
  
 +<WRAP center round tip 60%>
 you must launch after in a terminal the event :  you must launch after in a terminal the event : 
  
     signal-event nethserver-transmission-save     signal-event nethserver-transmission-save
 +</WRAP>
 +
  
 This event will read the **/var/lib/transmission/settings.json** and accordingly to these parameters will set good values to Nethserver (eg firewall, download folder....) This event will read the **/var/lib/transmission/settings.json** and accordingly to these parameters will set good values to Nethserver (eg firewall, download folder....)
  
 +  * Manual settings
 You will find some settings in the web application, nevertheless [[https://trac.transmissionbt.com/wiki/ConfigurationParameters|if you miss some specific]] then you must edit manually the /var/lib/transmission/settings.json **but it is a mandatory**, you must stop first the daemon You will find some settings in the web application, nevertheless [[https://trac.transmissionbt.com/wiki/ConfigurationParameters|if you miss some specific]] then you must edit manually the /var/lib/transmission/settings.json **but it is a mandatory**, you must stop first the daemon
  
Line 52: Line 56:
     signal-event nethserver-transmission-save     signal-event nethserver-transmission-save
  
- Once your torrents are downloaded you have two ways to retrieve them+====Retrieve Torrents==== 
 +Once your torrents are downloaded you have two ways to retrieve them
  
   * a samba share called transmission   * a samba share called transmission
Line 67: Line 72:
     signal-event nethserver-transmission-save     signal-event nethserver-transmission-save
  
 +====Allowed Users====
 at first only 'admin' is allowed to use them (think to set a password) but in the user panel you can allow more users at first only 'admin' is allowed to use them (think to set a password) but in the user panel you can allow more users
  
Line 72: Line 78:
   * Can use the Transmission WEB Folder   * Can use the Transmission WEB Folder
   * Can manage Transmission by the WebUI   * Can manage Transmission by the WebUI
 +====Reach Url====
 You have in the DashBoard -> Applications two urls to reach the WebUI and the Web-Folder You have in the DashBoard -> Applications two urls to reach the WebUI and the Web-Folder
 +else
 +
 +https://IP/dl-transmission
 +
 +https://IP/transmission
 +
 +and think about the transmission samba share
 +
 +====DB entries====
 +
 +see the different db properties
 +  # config show transmission
 +  transmission=configuration
 +    DownloadDir=/var/lib/transmission/Downloads   #folder where save downloads
 +    TCPPort=51413               #port opened to public to allow peers to connect to transmission, set a value or set it randomly in transmission
 +    WebNameDir=dl-transmission  #Url to retrieve downloads : https://IP/dl-transmission
 +    Webaccess=private           #the web service to retrieve download is restricted to the local network (public/private)
 +    access=public               #peer port opened to public
 +    status=enabled
 +
 +and the entries relative to the daemon
 +
 +   # config show transmission-daemon 
 +   transmission-daemon=service
 +     Name=transmission     #Url to reach transmission web application https://IP/transmission
 +     TCPPort=9091          #transmission port restricted to the localhost
 +     access=none           #transmission port restricted to localhost (it exist a reverse proxy)
 +     status=enabled
 +
 +
 +==== Issues ====
 +
 +Please raise Issues on [[https://github.com/stephdl/nethserver-transmission/issues|github]]
  
 +====RPM from geekery & EPEL====
 +  http://geekery.altervista.org/geekery/el6/x86_64/libevent2-2.0.10-1geekery.x86_64.rpm
 +  http://geekery.altervista.org/geekery/el6/x86_64/transmission-2.84-1geekery.x86_64.rpm
 +  http://geekery.altervista.org/geekery/el6/x86_64/transmission-cli-2.84-1geekery.x86_64.rpm
 +  http://geekery.altervista.org/geekery/el6/x86_64/repoview/transmission-common.html
 +  http://geekery.altervista.org/geekery/el6/x86_64/repoview/transmission-daemon.html
 +  https://dl.fedoraproject.org/pub/epel/6/x86_64/pwauth-2.3.10-5.el6.x86_64.rpm
 +  https://dl.fedoraproject.org/pub/epel/6/x86_64/mod_authnz_external-3.2.6-1.el6.x86_64.rpm
 {{tag>module}} {{tag>module}}
  
nethserver-transmission.1432243725.txt.gz · Last modified: 2019/06/05 19:48 (external edit)