transmission-web-control
docker-transmission-openvpn
transmission-web-control | docker-transmission-openvpn | |
---|---|---|
6 | 189 | |
4,505 | 3,969 | |
- | - | |
3.5 | 7.0 | |
28 days ago | 5 days ago | |
CSS | Shell | |
MIT License | GNU General Public License v3.0 only |
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.
docker-transmission-openvpn
-
'Canada Is a Video Piracy Hotspot While Brazil Sees Piracy in Decline'
I think you’re in a different bubble. If no one used vpn for torrents why is one of the top docker images for transmission one to support vpns? No ones spending money on a seed box that’s just casually torrenting.
https://github.com/haugene/docker-transmission-openvpn
- Routing torrenting on a home server through VPN
-
Tailscale vs Reverse proxy over HTTPS?
For torrent and open VPN this https://github.com/haugene/docker-transmission-openvpn is a great option if you can run docker.
-
VPN connection using Gluetun drops randomly every other day
I use haugene/transmission-openvpn to safely obtain all my Linux isos
-
Remember: Even on the High Seas, re-sharing is caring!
Link to github - https://github.com/haugene/docker-transmission-openvpn
-
Transmission (and Other) Notifications
I would try the absolute path of the script and see if that does it for you. I'm running transmission on docker using haugene/docker-transmission-openvpn and that's the absolute path within the container, but YMMV if you're running the program somewhere/somehow else.
- How does running qbitorrent and a VPN on a server work? What are the advantages?
- NordVPN with docker for torrenting | Transmission and QbitTorrent | Gluetun
- Hi I'm an idiot - Can someone give me a step-by-step walkthrough for installing a torrent client + bulletproof VPN on Docker?
-
I'm an idiot and need some experienced eyes to debug VPN and Gluetun crashing
I haven’t used GlueTUN so can’t help unfortunately but I do use this one - https://github.com/haugene/docker-transmission-openvpn and it seems easier and safer (the container stops if the VPN is down)
What are some alternatives?
transgui - 🧲 A feature rich cross platform Transmission BitTorrent client. Faster and has more functionality than the built-in web GUI.
nordvpn - NordVpn Docker Client
combustion - Simple, elegant testing for Rails Engines
synology-wireguard - WireGuard support for some Synology NAS drives
kettu - Rewrite of the Transmission Web Client with jQuery, Sammy and Mustache
docker-qBittorrentvpn - Docker container which runs a headless qBittorrent client with WebUI and optional OpenVPN
flood-for-transmission - A Flood (https://github.com/Flood-UI/flood) clone for Transmission
gluetun - VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.
combustion - Combustion is a sleek, modern web interface for Transmission
arch-delugevpn - Docker build script for Arch Linux base with Deluge, Privoxy and OpenVPN
Organizr - HTPC/Homelab Services Organizer - Written in PHP
docker-qbittorrentvpn - Docker container which runs a qBittorent-nox client with an optional WireGuard or OpenVPN connection