transmission-web-control
OS.js
transmission-web-control | OS.js | |
---|---|---|
6 | 24 | |
4,505 | 6,757 | |
- | 0.0% | |
3.5 | 0.0 | |
28 days ago | over 1 year ago | |
CSS | JavaScript | |
MIT License | GNU General Public License v3.0 or later |
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.
OS.js
- Os.js – open-source JavaScript web desktop platform with a window manager
- Show HN: PikaTorrent, a modern, multi-platform, open source BitTorrent app
- Os.js
- Why even have other programming languages?
-
Cloud Based Desktop Environment
OS.js
- Why can't there be one ubiquitous programming language that 'does everything' if the underlying principles of coding is all the same?
- Let's write Operating System in JavaScript
-
What did I do to deserve a JavaScript database?
You mean like https://www.os-js.org/ there are a few others also I believe.
What are some alternatives?
transgui - 🧲 A feature rich cross platform Transmission BitTorrent client. Faster and has more functionality than the built-in web GUI.
oneye
combustion - Simple, elegant testing for Rails Engines
Guacamole - The Guacamole project is now Apache Guacamole (http://guacamole.apache.org/). This repository has been repurposed as the base for the Apache Guacamole packages built for Glyptodon Enterprise.
kettu - Rewrite of the Transmission Web Client with jQuery, Sammy and Mustache
GateOne - Gate One is an HTML5-powered terminal emulator and SSH client
flood-for-transmission - A Flood (https://github.com/Flood-UI/flood) clone for Transmission
greenworks - a node.js plugin to integrate nw.js/electron games with steamworks
combustion - Combustion is a sleek, modern web interface for Transmission
puter - 🌐 The Internet OS! Free, Open-Source, and Self-Hostable.
Organizr - HTPC/Homelab Services Organizer - Written in PHP
purescript - A strongly-typed language that compiles to JavaScript