flood-for-transmission
transmission-web-control
| flood-for-transmission | transmission-web-control | |
|---|---|---|
| 5 | 6 | |
| 315 | 4,503 | |
| - | - | |
| 6.0 | 3.5 | |
| 28 days ago | 23 days ago | |
| Svelte | CSS | |
| GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
flood-for-transmission
- Docker No such file or directory
-
What Makes you Choose Your Current Client?
Idk I don't have much of a reason for them. One is my seedbox the other is connected to my NAS. I also use the Flood UI for my Transmission client running off my NAS in a Docker contaienr https://github.com/johman10/flood-for-transmission
- What's your preferred web UI torrent client?
-
I went a bit overboard customising Heimdall
Transmission also has alternative Web UIs that you can use: Combustion, Transmission Web Control, kettu and Flood for Transmission. The LinuxServer.io Transmission container has support for all of these.
-
need help finding a good looking and modern torrent client
- download the flood for transmission .zip folder (this is from a different repo - https://github.com/johman10/flood-for-transmission)
transmission-web-control
-
Show HN: PikaTorrent, a modern, multi-platform, open source BitTorrent app
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
-
I ditched those two and never looked back since
The remote UI was the one downside of Transmission, until this came out: https://github.com/ronggang/transmission-web-control
-
Transmission with Web Control
I have been able to install this: https://github.com/ronggang/transmission-web-control/wiki, in the transmission image.
-
I went a bit overboard customising Heimdall
Transmission also has alternative Web UIs that you can use: Combustion, Transmission Web Control, kettu and Flood for Transmission. The LinuxServer.io Transmission container has support for all of these.
-
Best Torrent Client?
UI is not too bad - docker container comes with bundled Transmission Web Control UI or standalone Transmission Remote GUI can be used on client...
-
Consider replacing BitTorrent and uTorrent with Transmission: a FOSS alternative
+1 for Transmission Remote GUI. Also, in a pinch, this web UI is quite a bit better than the default one: https://github.com/ronggang/transmission-web-control/wiki.
What are some alternatives?
flood - A modern web UI for various torrent clients with a Node.js backend and React frontend.
transgui - 🧲 A feature rich cross platform Transmission BitTorrent client. Faster and has more functionality than the built-in web GUI.
qBittorrent - qBittorrent BitTorrent client
combustion - Simple, elegant testing for Rails Engines
combustion - Combustion is a sleek, modern web interface for Transmission
kettu - Rewrite of the Transmission Web Client with jQuery, Sammy and Mustache
Organizr - HTPC/Homelab Services Organizer - Written in PHP
bt2qbt - bt2qbt is cli tool for export from uTorrent\Bittorrent into qBittorrent