deluge-to-rtorrent VS AriaNg

There is autodlirssi function in rutorrent which can drop automatic torrents to deluge, also there is postcompletion script which should help you move completed torrents to rtorrent if you wish to seed them longer. https://github.com/wseedbox/deluge-to-rtorrent you will need some minor fixes on path.

Hi I have been trying you use this script. https://github.com/wseedbox/deluge-to-rtorrent/blob/master/deluge_to_rtorrent.sh

You should use the deluge-to-rtorrent (instructions are also included) script to move torrents from Deluge to ruTorrent. I don't think this script allows you to move torrents specified by a tracker. At least that is what I realized from the script's description.

ruTorrent - I find Deluge starts to struggle when it's loaded with too many torrents. My rTorrent has over 4000 loaded with no slowdown in the UI. It's also useful to keep a separation from what I'm racing (I generally don't care to keep these files, they stay on my scratch drive). I move things from Deluge to here manually, though I have this script that automates it bookmarked to implement soon(tm).

if you use a rss reader,you can try [rsshub](rsshub.app/). for example,you can subscribe "https://github.com/mayswind/AriaNg/releases.atom" in your rss reader,when AriaNG is released,you will be noticed in your reader.

I'm using Aria2 on my server: https://aria2.github.io/ and add the GUI from here: https://github.com/mayswind/AriaNg/releases Actually this is working for a long time and I'm pretty happy with this combination...

Another one is AriaNG, pretty nice interface to your aria2 instance. You can export your configuration so you don't need to log-in on a new device every time. If you're using an Android phone, you can try Aria2App to control your download server remotely.

On your host machine (RPi, desktop, old laptop), you would need to run your services (paperless-ng, anything else you feel like, e.g. filebrowser, navidrome, Jellyfin, qBittorrent, Aria2Ng) which (best practice) is to serve to localhost/127.0.0.1 and then you use nginx to connect localhost:port to sensible addresses on LAN or a small homepage, which are then forwarded to your router, which is then connected to dyndns.