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

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

Added part for debian testing


  • Installing/Linux/Debian/Wheezy

    v2 v3  
    2323apt-get install -t precise libtorrent-rasterbar6 python-libtorrent 
     27= Debian Jessie (testing) with systemd = 
     28(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..) 
     30This 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) 
     32== Install == 
     34To get the binaries, simply do: 
     36apt-get update 
     37apt-get install deluged deluge-web 
     39(Don't use the `deluge-webui` package anymore) 
     41Create a new user to run deluged: 
     43adduser --disabled-password --system --home /opt/deluge --gecos "Deluge server" --group deluge 
     46Get rid of the old init files (we'll use systemd) if they exist 
     48mkdir -p /opt/deluge/bkup/etc/init.d 
     49mkdir -p /opt/deluge/bkup/etc/default 
     50mv /etc/init.d/deluged /opt/deluge/bkup/etc/init.d 
     51mv /etc/default/deluged /opt/deluge/bkup/etc/default 
     53(there might be a restart required to get rid of the old setting from /etc/default/deluged that prevents the service to stat up) 
     55Create new systemd service files similar as described [UserGuide/InitScript/systemd here] (but slightly modified; save them in `/etc/systemd/system`): 
     57`nano /etc/systemd/system/deluged.service` 
     60Description=Deluge Bittorrent Client Daemon 
     66ExecStart=/usr/bin/deluged -d -c /opt/deluge -L error -l /var/log/deluge/deluged.log 
     73`nano /etc/systemd/system/deluge-web.service` 
     76Description=Deluge Bittorrent Client Web Interface deluged.service 
     83ExecStart=/usr/bin/deluge-web -c /opt/deluge -L error -l /var/log/deluge/deluged.log 
     89Touch the log files: 
     91mkdir /var/log/deluge 
     92touch /var/log/deluge/deluged.log /var/log/deluge/deluge-web.log  
     93chown -R deluge:deluge /var/log/deluge* 
     96Now test the install and create an initial config folder: 
     98systemctl start deluged 
     99systemctl status deluged 
     102The 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` 
     105== Config == 
     106This part basically sums up [UserGuide/ThinClient], [UserGuide/InitScript] and [UserGuide/Authentication]. 
     108Create users with authentication levels (for the GUI applications, NOT for the web frontend): 
     110echo "AdminAlice:password:10" >> /opt/deluge/auth 
     111echo "UserBob:password:5" >> /opt/deluge/auth 
     112echo "WatchingOnlyCarol:password:1" >> /opt/deluge/deluge/auth 
     115If 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: 
     116`nano /opt/deluge/.config/deluge/core.conf` 
     118Here 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. 
     121== Enable the service == 
     123Enable the services to start up on boot: 
     125systemctl enable deluged 
     126systemctl enable deluge-web 
     129Check if it's running with: 
     131systemctl status deluged 
     132systemctl status deluge-web 
     134and 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`), 
     135add your server ip, port (default 58846), username and password. 
     137IMPORTANT: change the password of the web interface (default: `deluge`) 
     139If it doesn't work check with `systemctl status ...` and double check your access rights. 
     141== Cavehat == 
     142If 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.