I need reviews and tests on a new module I’m working on : nethserver-transmission
yum install http://mirror.de-labrusse.fr/nethserver/nethserver-transmission/nethserver-transmission-1.0.1-2.ns6.noarch.rpm http://mirror.de-labrusse.fr/nethserver/nethserver-transmission/libevent2-2.0.10-1geekery.x86_64.rpm http://mirror.de-labrusse.fr/nethserver/nethserver-transmission/transmission-2.84-1geekery.x86_64.rpm http://mirror.de-labrusse.fr/nethserver/nethserver-transmission/transmission-cli-2.84-1geekery.x86_64.rpm http://mirror.de-labrusse.fr/nethserver/nethserver-transmission/transmission-common-2.84-1geekery.x86_64.rpm http://mirror.de-labrusse.fr/nethserver/nethserver-transmission/transmission-daemon-2.84-1geekery.x86_64.rpm http://mirror.de-labrusse.fr/NethServer/6/x86_64/pwauth-2.3.10-5.el6.x86_64.rpm http://mirror.de-labrusse.fr/NethServer/6/x86_64/mod_authnz_external-3.2.6-1.el6.x86_64.rpm
after that the transmission-daemon is started, go to https://IP/transmission
if you want to stop it (enabled/disabled)
config setprop transmission-daemon status disabled
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 :
- the rpc-peer (peer port 51413 by default)
- the download folder (/dl-transmission by default)
- the rpc-url (/transmission by default)
- the daemon port (9091 by default)
you must launch after in a terminal the event :
signal-event nethserver-transmission-save
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…)
You will find some settings in the web application, nevertheless 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
service transmission-daemon stop
vim /var/lib/transmission/settings.json
save and launch the event nethserver-transmission-save (to reconfigure accordingly the nethserver)
signal-event nethserver-transmission-save
Once your torrents are downloaded you have two ways to retrieve them
- a samba share called transmission
- a web folder restricted to the local network https://IP/dl-transmission
if you want to allow it to the WWW (public/private)
config setprop transmission Webaccess public
signal-event nethserver-transmission-save
if you want to stop all samba and web folder (enabled/disabled)
config setprop transmission status enabled
signal-event nethserver-transmission-save
at first only ‘admin’ is allowed to use them (think to set a password) but in the user panel you can allow more users
- Can use the Transmission SMB Folder
- Can use the Transmission WEB Folder
- Can manage Transmission by the WebUI
You have in the DashBoard -> Applications two urls to reach the WebUI and the Web-Folder