Skip to content
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

Feature request: portable version / save settings to local folder [Windows] #1761

Closed
vatterspun opened this issue Dec 2, 2015 · 4 comments
Closed

Comments

@vatterspun
Copy link

vatterspun commented Dec 2, 2015

Current behavior: settings are written to the ".Tribler" folder in AppData

Requested capability: settings written to the local folder.

Why? One additional layer of security/convenience is the ability to run the client via a USB drive or over cloud services. Right now, if the program is run from anywhere but the same computer, you will have to re-enter the settings, which can become a chore. This approach also simplifies backup/restore and synchronization between machines.

Notably this can make updating the client more complicated as you have to know to update some files and not others, so it is recommended as an optional setting or separate version.

@whirm
Copy link
Contributor

whirm commented Dec 3, 2015

Maybe a TRIBLER_HOME env. var could be added so that Tribler will use that instead of the default state dir path. On Linux this can already be done by calling Tribler like this: HOME=/media/usb_drive/my_tribler_dir tribler

We won't give a lot of priorty to this, but we will welcome a pull request for that.

Thanks for the report!

@ichorid
Copy link
Contributor

ichorid commented Aug 5, 2019

Related to #3904

@vatterspun
Copy link
Author

So did this get resolved? I didn't see a clear bath to settings portability in the #3904 thread. Thanks.

@devos50
Copy link
Contributor

devos50 commented Jan 21, 2020

@vatterspun not yet, but I think #3904 covers this issue sufficiently well. We will try to prioritize this after the 7.5 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants