rtinst VS flood

I installed rtorrent and rutorrent using https://github.com/arakasi72/rtinstbut I tried mounting webdave and cifs to the download folder so my downloads wouldn't use the system drive but it failed rtorrent was shutdown. I had to unmount the directory to start it any suggestions?

Other option is to install rtinst https://github.com/arakasi72/rtinst after script installation, just do rtdload when it asks just input y and you will have https:///download with username and password you set up for rutorrent.

If you need just run a rTorrent + FTP you can use https://github.com/arakasi72/rtinst (is small but powerfull)

https://www.delimiter.com/plex-hosting/ <- You could try them out if you want to use a script like https://swizzin.ltd/ or https://github.com/arakasi72/rtinst for easy setup of the torrent portion of the box.

Why bake libtransmission into the app instead of just using the transmission daemon's RPC?

What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.

I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]

1: https://github.com/transmission/transmission/blob/main/docs/...

1: https://github.com/jesec/flood

2: https://github.com/ronggang/transmission-web-control

Only one that I'm aware of is Flood: https://github.com/jesec/flood

If you haven't seen the https://flood.js.org project before. It has subjectively a nicer ui and works with qbittorent.

You can install alternate web UIs very easy. I’m a big fan of Flood, which is mobile friendly: https://flood.js.org/

One note: I lean heavily on an API to manage it so I'd love to continue using flood, I tested qbittorrent with it briefly and it didn't go well.

You mean a torrent client? I’m using rTorrent with Flood (the new jesec fork that’s actually active) and it works brilliantly on mobile

https://flood.js.org/ ?

If it's just the web ui you're worried about perhaps look into installing Flood & see if it helps? It's going to be a better web ui overall. (I've never needed to use it personally but it's been recommended in the pat)

qbitorrent-nox with flood-ui

Impressive. But I dont get why they would rebuild the web client when there are existing options like: https://github.com/jesec/flood