Changes between Version 2 and Version 3 of Installing/Linux/Debian/Wheezy

Timestamp:

08/21/2014 01:59:04 AM (9 years ago)

Author:

rafik

Comment:

Added part for debian testing

Installing/Linux/Debian/Wheezy

@@ -23 +23 @@
 apt-get install -t precise libtorrent-rasterbar6 python-libtorrent
 }}}
+
+
+= Debian Jessie (testing) with systemd =
+(Note for admins: I'm sorry I can't create a new page, so I'm attaching it here, please move to where ever it's ok. And I'm a beginner, so maybe I do something that's not considered good practice or completely wrong..)
+
+This describes the install of deluged for a headless server with webui running Debian Jessie using the default package version of deluge (this means you won't get an up to date version, but it'll be updated automatically with your system)
+
+== Install ==
+
+To get the binaries, simply do:
+{{{
+apt-get update
+apt-get install deluged deluge-web
+}}}
+(Don't use the `deluge-webui` package anymore)
+
+Create a new user to run deluged:
+{{{
+adduser --disabled-password --system --home /opt/deluge --gecos "Deluge server" --group deluge
+}}}
+
+Get rid of the old init files (we'll use systemd) if they exist
+{{{
+mkdir -p /opt/deluge/bkup/etc/init.d
+mkdir -p /opt/deluge/bkup/etc/default
+mv /etc/init.d/deluged /opt/deluge/bkup/etc/init.d
+mv /etc/default/deluged /opt/deluge/bkup/etc/default
+}}}
+(there might be a restart required to get rid of the old setting from /etc/default/deluged that prevents the service to stat up)
+
+Create new systemd service files similar as described [UserGuide/InitScript/systemd here] (but slightly modified; save them in `/etc/systemd/system`):
+
+`nano /etc/systemd/system/deluged.service`
+{{{
+[Unit]
+Description=Deluge Bittorrent Client Daemon 
+After=network.target
+
+[Service]
+User=deluge
+Type=simple
+ExecStart=/usr/bin/deluged -d -c /opt/deluge -L error -l /var/log/deluge/deluged.log
+
+[Install]
+WantedBy=multi-user.target
+}}}
+
+
+`nano /etc/systemd/system/deluge-web.service`
+{{{
+[Unit]
+Description=Deluge Bittorrent Client Web Interface
+After=network.target deluged.service
+Requires=deluged.service
+
+[Service]
+User=deluge
+Type=simple
+ExecStart=/usr/bin/deluge-web -c /opt/deluge -L error -l /var/log/deluge/deluged.log
+
+[Install]
+WantedBy=multi-user.target
+}}}
+
+Touch the log files:
+{{{
+mkdir /var/log/deluge
+touch /var/log/deluge/deluged.log /var/log/deluge/deluge-web.log 
+chown -R deluge:deluge /var/log/deluge*
+}}}
+
+Now test the install and create an initial config folder:
+{{{
+systemctl start deluged
+systemctl status deluged
+}}}
+
+The status should return something along `active (running)` in green. There should be several config files and folders in `/opt/deluge`. Stop it again: `systemctl stop deluged`
+
+
+== Config ==
+This part basically sums up [UserGuide/ThinClient], [UserGuide/InitScript] and [UserGuide/Authentication].
+
+Create users with authentication levels (for the GUI applications, NOT for the web frontend):
+{{{
+echo "AdminAlice:password:10" >> /opt/deluge/auth
+echo "UserBob:password:5" >> /opt/deluge/auth
+echo "WatchingOnlyCarol:password:1" >> /opt/deluge/deluge/auth
+}}}
+
+If you are not connecting over ssh, then you should enable remote access. To do so change the according entry (`allow_remote`) in the config file:
+`nano /opt/deluge/.config/deluge/core.conf`
+
+Here you can also change ports, incoming files directories and so on if you desire. You could also connect with the web interface or the gui and do the changes there.
+
+
+== Enable the service ==
+
+Enable the services to start up on boot:
+{{{
+systemctl enable deluged
+systemctl enable deluge-web
+}}}
+
+Check if it's running with:
+{{{
+systemctl status deluged
+systemctl status deluge-web
+}}}
+and of course with your webbrower: `http://server:8112` for the web interface and / or with your local deluge install (after disabling classic mode under `Preferences > Interface`),
+add your server ip, port (default 58846), username and password.
+
+IMPORTANT: change the password of the web interface (default: `deluge`)
+
+If it doesn't work check with `systemctl status ...` and double check your access rights.
+
+== Cavehat ==
+If you do a system update `apt-get upgrade` and there's a new version around, it could be that the default init files are regenerated.