Optional Features¶
Enabling Optional Applications¶
To activate the optional applications, add these settings to your
host_vars
:
flexget_enabled: yes
for FlexGet.rutorrent_enabled: yes
for ruTorrent.
Read the following sections for details.
Installing FlexGet¶
After setting flexget_enabled: yes
, run the playbook again.
FlexGet is just installed ready to be used, for full operation a
configuration file located in ~/.config/flexget/config.yml
must be
added (see the FlexGet cookbook). A cronjob is provided too (called
every 11 minutes), but only starts to actually call FlexGet after you
add that configuration file.
Look into the files
~/.config/flexget/flexget.log
and
~/.config/flexget/flexget-cron.log
to diagnose any problems.
Hint
Running FlexGet with Python 3
If your target host has Python 3.6+ installed (i.e. runs Bionic or Buster),
you can use that for the FlexGet venv by changing venv_bin
in your host_vars
:
venv_bin: "python3 -m venv"
Note that the latest versions of FlexGet require Python 3, i.e. you’ll get an older release if you stick to Python 2.
On older releases of Ubuntu (Xenial), you can install Python 3.7 or higher from the DeadSnakes PPA. For your convenience, the basic installation on Ubuntu already adds Python 3.7 from there.
Make sure to include the minor version in your configuration then:
venv_bin: "python3.7 -m venv"
Also, check beforehand if the ssl
module is supported:
python3.7 -m ssl
If you get an error message that _ssl
is not available,
you cannot use that Python build for https
RSS feeds.
Installing and Updating ruTorrent¶
The ruTorrent web UI is an optional add-on, and you have to activate it
by setting rutorrent_enabled
to yes
and providing a
rutorrent_www_pass
value, usually in your
host_vars/my-box/main.yml
and host_vars/my-box/secrets.yml
files, respectively. Then run the playbook again.
Alternatively to the self-signed certificate that is created for Nginx,
you can also copy a certificate you got from other sources to the paths
/etc/nginx/ssl/cert.key
and /etc/nginx/ssl/cert.pem
.
See this blog post if you want excessive detail on secure HTTPS setups.
After the second run, ruTorrent is available at
https://my-box.example.com/rutorrent/
(use you own domain or IP in
that URL).
To update to a new version of ruTorrent, first add the desired version
as rutorrent_version
to your variables – that version has to be
available on GitHub Releases. Then move the old installation tree away:
cd ~rutorrent
mv ruTorrent-master _ruTorrent-master-$(date "+%Y-%m-%d-%H%M").bak
tar cfz _profile-$(date "+%Y-%m-%d-%H%M").bak profile
Finally, rerun the playbook to install the new version. In case anything goes wrong, you can move back that backup you made initially.