originally the intention was to have a very simple, convenient and sort of containerized thing, that downloads arbitrary torrent content in a fully automated way. One could say, it is a headless bulk downloader for torrents. It was intended for making my first steps in the golang world (which is still a future work). For now the core logic is written in shell script and daemonized by systemd.
- opens up a VPN connection to IPredator
- watches for torrent files and magnets, downloads their content and then shares it with the host system
- btfs
- OpenVPN
- ferm (firewall)
- DNScrypt Proxy
-
clone the repo
-
add the file
./conf/IPredator.auth
containingUSERNAME PASSWORD
-
adjust desired configurations (
./conf
) -
run
vagrant up
from within./vm
-
wait until the provisioning has finished and then spin up the vm again
Just put .torrent
files into the shared folder (or folders with such files) or paste
magnet links into the corresponding file ./share/magnet-links
... and wait.
- after the provisioning has finished, the vm will be shutdown, just to make sure everything comes up as expected after the installation (e.g. mounting synced folders). So in order to use this whole thing, one has to get the machine up and running again
- the provisioning was originally based on IPredator HOWTOs
- vagrant documentation and CLI
-
vagrant + ubuntu 16.04 aren't good friends quite yet. So the provisioning might fail on first startup (you will notice errors during the boot process and by finishing of unnaturally fast). A reboot before starting the provision might solve the problem.
vagrant up --no-provision vagrant halt vagrant up --provision
- switching form upstart to systemd
- remove the hard-coded IPredator support, to enable other VPN providers
- support magnet links (not only torrent files)
- check for version of files loaded from IPredator
- write the core logic in golang
- eventually moving from ubuntu to debian
- containerize this whole thing
- move the firewall switch (
fermreload.sh
) to a systemd unit/service
- the provisioning can be kind of unstable. If it breaks, please destroy the machine and have another try