Differences between revisions 23 and 24
Revision 23 as of 2018-07-23 06:30:50
Size: 4513
Editor: PeeKaa
Comment: other possibility accessing daemon
Revision 24 as of 2018-07-23 06:40:25
Size: 4675
Editor: PeeKaa
Comment: server install
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
 * DebianPkg:transmission-daemon - A !BitTorrent daemon using a web interface.
== Server installation ==
On server you can install !BitTorrent daemon using a web interface by `apt` with suggested packages cause you might to need upnp and other things.

{{{
apt install transmission-daemon --install-suggests
}}}

Translation(s): English - Español - Italiano


https://upload.wikimedia.org/wikipedia/commons/archive/6/6d/20180717025232!Transmission_icon.png

About

Transmission is a light-weight and cross-platform BitTorrent client with full encryption, DHT, µTP, PEX and Magnet Link support. It is the default BitTorrent client for DebianGnome.

Installation

if you have installed your DebianGnome desktop from tasksel then transmission-gtk should be installed by default, but it is possible to use one more of the following packages, depending on your requirements:

Server installation

On server you can install BitTorrent daemon using a web interface by apt with suggested packages cause you might to need upnp and other things.

apt install transmission-daemon  --install-suggests

Configuration

The transmission-gtk and transmission-qt clients can be configured via the application or via ~/.config/transmission/settings.json.
The transmission-daemon can be configured by editing /etc/transmission-daemon/settings.json.

Configuration settings.json

Changes made manually to the file /etc/transmission-daemon/settings.json while the daemon is running will be silently overwritten on transmission exit. You need to stop it first, make changes and start it again.

service transmission-daemon stop
mcedit mcedit /etc/transmission-daemon/settings.json
service transmission-daemon start

The setting.json file is quite self explanatory but the common things that might need editing are:
(Full explanation here https://github.com/transmission/transmission/wiki/Editing-Configuration-Files):

  • "download-dir": "/var/lib/transmission-daemon/downloads": the location of the finished downloads
  • "rpc-password": "*(Hh09ajdf-9djfd89ash7a8ggG&*g98h8009hj90": the password for the web interface, replace the hash with a plain text password and it will be hashed on reload

  • "rpc-username": "transmission": user name for web interface
  • "rpc-whitelist": "127.0.0.1": IP's allowed to access the daemon, something like "rpc-whitelist": "127.0.0.1,192.168.*.*", is the formatting for the IP addresses

Change default user on daemon

In case you want to set a different user than the default debian-transmission user, you need to create a configuration file to overwrite default settings.

# systemctl edit transmission-daemon.service
# Then add these lines:
[Service]
User=USER

Where "USER" is the name of the user you want to run the daemon as.
The file is located then here /etc/systemd/system/transmission-daemon.service.d/override.conf.
Or you can edit directly file /etc/systemd/system/multi-user.target.wants/transmission-daemon.service.

Change permission on download directory

If you have transmision on server, you would like to edit downloaded files from local stations. Good choice is to make download directory editable by a group of your stations users.

Change umask in settings.json to umask = 0 or even umask=7 (decimal explanation, the json markup language only accepts numbers in base 10). Finally change umask of the transmission daemon by adding UMask=007 to /etc/systemd/system/multi-user.target.wants/transmission-daemon.service, change permission of the download directory and probably change group of transmission daemon default user.

Connecting to daemon

Web Interface

Once the daemon is running, it can be accessed from your web browser by pointing it at http://127.0.0.1:9091 or if you come from local network http://ip-address-of-server:9091 (once you have whitelisted the IP range).

Command line app CLI and TUI

For connecting to daemon from shell you can use stig https://github.com/rndusr/stig. You can manipulate torrents and get stats. F.e. by stig ls active you get active torrents.

Other possibility

The are plenty of other ways how to access daemon - see https://transmissionbt.com/resources/.

External Links


CategorySoftware