transmission-web-control
combustion
| transmission-web-control | combustion | |
|---|---|---|
| 6 | 3 | |
| 4,503 | 696 | |
| - | - | |
| 3.5 | 5.8 | |
| 24 days ago | about 1 month ago | |
| CSS | Ruby | |
| MIT License | 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.
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.
combustion
-
Railsapps Obituary
I don't find this that bad, once I got used to it. There is a third-party gem, combustion that tries to help you avoid this. But after trying it out in a few projects, I mostly tried to just skip it and do it the Rails way.
-
What’s the best way to test a gem that integrates with Rails?
if you want the smallest possible dummy app, provided by a gem, see combustion. It does work well with appraisal for testing against multiple versions of Rails, which someone else mentioned.
What are some alternatives?
transgui - 🧲 A feature rich cross platform Transmission BitTorrent client. Faster and has more functionality than the built-in web GUI.
flood-for-transmission - A Flood (https://github.com/Flood-UI/flood) clone for Transmission
kettu - Rewrite of the Transmission Web Client with jQuery, Sammy and Mustache
Transmissionic - Remote for Transmission Daemon
flood - A web UI for rTorrent, qBittorrent and Transmission with a Node.js backend and React frontend. Migrate to v4: https://github.com/jesec/flood/wiki/Migrate-from-older-versions-of-Flood.
combustion - Combustion is a sleek, modern web interface for Transmission
good_job - Multithreaded, Postgres-based, Active Job backend for Ruby on Rails.
Organizr - HTPC/Homelab Services Organizer - Written in PHP
Appraisal - A Ruby library for testing your library against different versions of dependencies.
bt2qbt - bt2qbt is cli tool for export from uTorrent\Bittorrent into qBittorrent
pikatorrent - BitTorrent client ⚡. For mobile, desktop & server.