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

[proxallium] ProxAllium can't save configuration in default install location #2

Closed
TheDcoder opened this issue Sep 21, 2021 · 10 comments
Assignees
Labels
bug Something isn't working

Comments

@TheDcoder
Copy link

The default install location seems to be unwritable without admin privileges, so none of the configuration is saved and ProxAllium "forgets" every time it is restarted.

Is it possible to change the default location to somewhere writable like %AppData%? Or if chocolatey permits it, changing the permissions of the install folder.

As it is a portable application, it uses the same directory for storing all configuration.

@Cossey
Copy link
Owner

Cossey commented Sep 21, 2021

Okay, I will look into what's required from Chocolatey to install into AppData and give that ago.

@Cossey Cossey self-assigned this Sep 21, 2021
@Cossey Cossey added bug Something isn't working in progress This is being actively worked on labels Sep 21, 2021
@Cossey
Copy link
Owner

Cossey commented Sep 21, 2021

Okay, I have made further improvements to the package install process. The files will be installed to the Roaming App Data folder. Instead of the files being included separately I package the 7z from Github and extract that to the destination folder using the chocolatey tools. The package version is modified to use the package fix version notation in this version. I will push code soon. It might take a while to get this version approved and available on chocolatey.

@TheDcoder
Copy link
Author

Thanks!

I am planning to release an update soon (as time permits), let me know if there is anything I can change or add to improve support for chocolatey.

@Cossey
Copy link
Owner

Cossey commented Sep 23, 2021

I don't think there's anything that needs to be added to improve support - unless you want the ability to pass through configuration variables from the chocolatey command line.

@TheDcoder
Copy link
Author

Good to know, I'll pass on the command line configuration integration, most users wouldn't be interested in that :)

@Cossey Cossey closed this as completed in 45e8cba Sep 26, 2021
@TheDcoder
Copy link
Author

I released a new version: v0.4.3

I hope this won't interfere with your chocolatey script updates.

@Cossey
Copy link
Owner

Cossey commented Sep 26, 2021

No it's fine. You'll need to let me know if you change the exe name or shift away from 7z. If the folder structure is the same it will still be okay.

Note: I can't submit this version until the fixed package I submitted the other week gets approved first. This could take a while and is dependent on the moderators approving these packages when they get flagged on VirusTotal.

@TheDcoder
Copy link
Author

@Cossey I noticed that the reviewer in the community repo is waiting for your response regarding your PS script, looks like this version will get rejected if you don't respond within 15 days:

We've found proxallium v0.4.3 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

No hurry but I thought I'd let you know :)

@Cossey
Copy link
Owner

Cossey commented Oct 28, 2021

Thanks, just been a little busy. Will look into this now.

@Cossey
Copy link
Owner

Cossey commented Nov 8, 2021

All done, updated and approved. It will install to the chocolatey tools folder as per moderator request. This folder has write permissions for standard users.

@Cossey Cossey removed the in progress This is being actively worked on label Nov 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants