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

Absolute paths in INI breaking ProxAllium after relocation #1

Closed
Songersoft opened this Issue Jul 16, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@Songersoft
Copy link

Songersoft commented Jul 16, 2017

I relocated my ProxAllium on my hard drive (I moved the folder)

After the move ProxAllium ini needed updated. Just letting you know. Maybe if ProxAllium doesn't find Tor it will recheck the root folder and update the ini.

@TheDcoder TheDcoder self-assigned this Jul 17, 2017

@TheDcoder TheDcoder added the bug label Jul 17, 2017

@TheDcoder

This comment has been minimized.

Copy link
Member

TheDcoder commented Jul 17, 2017

Ah! An excellent find! ProxAllium automatically writes the absolute location of the tor executable in the ini file, maybe I can make it use relative paths...

I'll see what I can do, thanks for the report!

@TheDcoder TheDcoder changed the title ini and moving ProxAllium folder Absolute paths in INI breaking ProxAllium after relocation Jul 17, 2017

@TheDcoder

This comment has been minimized.

Copy link
Member

TheDcoder commented Jul 24, 2017

I am reluctant to fix this problem because I am planning to make an automatic Tor management system which would download/detect/update Tor automatically for the user, this feature would make this bug redundant.

For anyone with this problem, they can just delete config.ini and config.torrc so that ProxAllium can regenerate them with the new paths... and of course it can also be done manually by changing the paths in the INI and torrc files 😉

@TheDcoder TheDcoder added this to the v0.3 milestone Jul 24, 2017

@TheDcoder

This comment has been minimized.

Copy link
Member

TheDcoder commented Aug 30, 2017

I have just pushed a commit which fixes this bug by using relative paths in config.ini. The fix will be included in the next release.

You can download the fixed source code if you want to test it out, also includes new features 😉

@TheDcoder TheDcoder closed this Aug 30, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.