-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transmission integration #13
Comments
Yes this is possible. Transmission has an Api that provides basic interaction https://trac.transmissionbt.com/browser/trunk/extras/rpc-spec.txt Although i would rather work with a torrent app that supports all major operating systems (windows, linux, osx). Transmission is not available on windows. I do not use torrents myself so i will not be working on this any time soon. If anyone would like to work on this feature, please do so and send me a pull request. |
A port of transmission is very much so available on Windows (http://sourceforge.net/projects/trqtw/) and there is not many other torrent client/servers providing a good embedded experience that you're probably looking for when setting up these kind of servers, especially available on all platforms. |
I think that most people that use torrents with SickBeard/CouchPotato use transmission as their client. Hopefully somebody can add support for it soon as it is the only thing holding me back from using this! |
Well, considering most the people who use this application stack host it in a LAMP box, yeah, Transmission would seem to be the order of the day. |
I guess that you will cover most users supporting both Transmission and uTorrent. |
Well Junal... You just start writing ;) |
The problem with this is, i would also need to create a torrent searcher. Just like newznab is now. I do not know what torrent searcher to use right now. This would also make it complicated for users having both sabnzbd and torrent (transmission) Then there would be 2 download applications. Bottomline: this could be a good idea but we need to think this through. |
uTorrent would be highly appreciated too (as this is the most commenly used torrent client on windows) |
I think deluge would be the better fit to integrate with this project. It's written in python, open source and cross platform. |
uTorrent integration would be great! |
Looks great! |
I have to look into the uTorrent Api before i can 100% confirm that, but to support a windows torrent client i want to use uTorrent if possible. |
First show download speed, then upload speed
Basic torrent usage has been added to the master branch. Please let me know what you think and if it works for you. |
From now on this issue is Transmission only. For uTorrent integration see #71 |
Thanks styxit, this works great on my Raspberry Pi with a transmission daemon running on debian-based Raspbmc. Only thing missing is a dashboard widget! 👍 |
I am thinking about making some smaller, aesthetic changes to the Transmission UI, so styxit, if you have any preference out of these, please note :)
|
As long as it improves usability and can benefit all users it is fine with me. I do not even use the transmission part myself. I created it because there were so many people asking for it and no one else was willing to do it at that time. I would love to see your ideas! |
I dont know if its possible, but for all other applications I see you have an option for rpc through proxy. In the config file of transmission, I have setup : "rpc-url: "/transmission/" When i do a proxy & proxy reverse through port 80, on "domain.nl/transmission/" Transmission works without problems. But when I enter transmission settings in htpc manager, i cant get connection. Am i missing the option for url rewrite for transmission? Or am i doing something wrong? The ref for rpc can be found here: |
http://ip:port/transmission/rpc is hardcoded into the module. Why are you accessing this via a reverse proxy and not directly? |
Okay so the proxy forward / reverse works by default on the name transmission. The only thing that does not work is when I click the transmission link in the header of htpc manager , it does not open the proxy forward/reverse folder.. It just opens the main domain. Why i proxy forward it all? Cause then I can reach it from the outside without opening additional ports.. When i'm on the boat, and I want to connect to home to htpc manager, I need to open up that port.If I route it through a proxy reverse.. Its " not" so obvious that im running transmission, and I don't need to be worried about blocked ports in the harbor. So basically, what i have done is: http://mydomain.nl/htpcmanager/ All on port 80. all password secured. If i have all these apps connecting through the above folders through proxy forward.. every app is available on the internet without me remembering ports and so on :). |
Ok, it's easy to fix. |
@cyberb0b Okei, it wasnt so easy to fix.. I have no idea how to solve issue regarding session id. Just a quick question do you change the transmission internal bathpath? Can you login to transmission via the reverse prox and give me the full url to transmission (just mask the domain name, i dont need that one) |
http://www.xxxxxxxx.nl:9091/transmission/web/ (not reachable from the outside) in the config of transmission I have set "rpc-url" /transmission/ This option is not available in the gui, I have set this in the config file. Uhh.. probably you need to add /web/ behind it. transmission by default has its api on /transmission/ |
Basic version for transmission on osx is now working
To-do:
The text was updated successfully, but these errors were encountered: