Page 3 of 3

Re: Deluge (torrent client)

Posted: Sun Oct 04, 2015 12:42 pm
by the_watcher
Midas wrote:I haven't tested it, but if you're launching Deluge with a batch file, you might be able to change that location with a local variable.

So, assuming your batch is inside Deluge's folder and there's a 'config' sub-folder, you could have this in your batch:
For this to work, you need to leave the original key value intact:
  • Code: Select all

    appDataPath = os.environ.get("APPDATA")
Yes, that seems to work, Midas. So you can totally ignore the common.py instructions i posted above,
and just create a batch file with this code:

Code: Select all

SET APPDATA=%~dp0\config
start deluge.exe -c "config\deluge"
I don't know that much about batch files, so i followed the common.py file
guidelines to do it. Your method is definitely much simpler 8)

For the registry stuff and the recently-used.xbel file in \user\current\AppData\Local,
i suppose we need a wrapper...

Re: Deluge (torrent client)

Posted: Mon Oct 05, 2015 9:36 am
by Midas
the_watcher wrote:Yes, that seems to work, Midas.

[...]

For the registry stuff and the recently-used.xbel file in \user\current\AppData\Local, i suppose we need a wrapper...
Great. 8)

And if you provide details of those registry keys, I could assemble a yaP launcher config for you to test...

Re: Deluge (torrent client)

Posted: Thu Oct 08, 2015 11:41 am
by the_watcher
Awesome, Midas.
However, i'm not aware of any registry entries myself.
Giulia asked about the registry, i've just replied to him/her, perhaps he/she could clarify a bit more.

Re: Deluge (torrent client)

Posted: Fri Oct 09, 2015 5:04 am
by Midas
OK. 8)

Re: Deluge (torrent client)

Posted: Mon Aug 01, 2016 2:34 pm
by webfork
I updated the entry a little bit:

1. I'm directly linking to the download. I found the process and exact EXE file to grab confusing so I'm trying to save users time.
2. The "_outdir" directory didn't show up in my testing so I put in an "if" statement.
3. Minor entry edit

EDIT: I'm glancing back through this thread and I'm not clear on whether the -c data argument is enough to resolve portability issues. Should this be in the database?

Re: Deluge

Posted: Mon Aug 01, 2016 2:57 pm
by smaragdus
@webfork

You are right- I spotted this several hours ago when I extracted the installer but I forgot to report it. When the installer (deluge-1.3.13-win32-py2.7-0) is extracted by 7-Zip 16.02 there is no $_OUTDIR folder.

I am not a portability specialist but

Code: Select all

 -c data
really creates data folder containing program's setting. So used without plug-ins Deluge is portable and my opinion is that it should stay in the database.

Re: Deluge 1.3.14

Posted: Mon Mar 06, 2017 3:19 pm
by smaragdus
Deluge at version 1.3.14, all downloads, Windows downloads and changes:
Deluge 1.3.14 (6 March 2017)

Core
  • #2889: Fixed 'Too many files open' errors.
  • #2861: Added support for python-geoip for use with libtorrent 1.1.
  • #2149: Fixed a single proxy entry being overwritten resulting in no proxy set.
UI
  • Added tracker_status translation to UIs.
GtkUI
  • #2901: Strip whitespace from infohash before checks.
  • Add missed feature autofill infohash entry from clipboard.
WebUI
  • #1908: Backport bind interface option for server.
  • Security: Fixed WebUI CSRF Vulnerability.
ConsoleUI
  • #2948 [Console] Fix decode error comparing non-ascii (str) torrent name.
AutoAdd? Plugin
  • Fixes for splitting magnets from file.
  • Remove duplicate magnet extension when splitting.

Re: Deluge 1.3.14

Posted: Mon Mar 06, 2017 11:29 pm
by SYSTEM
smaragdus wrote:Deluge at version 1.3.14, all downloads, Windows downloads and changes:
Thanks. Entry updated. :)

Re: Deluge (torrent client)

Posted: Tue Jun 18, 2019 9:05 pm
by billon
Latest version is 2.0.3 (2019-06-12), but:
https://deluge.readthedocs.io/en/latest/intro/01-install.html#i-class-fa-fa-windows-i-windows wrote: Unfortunately due to move to GTK3 and Python 3 there is no installer package currently available for Windows.

Intrepid users can install Deluge from separate packages as detailed in issue #3201.