Portable versions should store their configuration in program directory

[SudoerReodus]

Feature description | توضیحات ویژگی

Currently the portable versions store their configuration in user home directory, rather than in the program directory itself.
This is undesirable.

1- Having the configs stored alongside the program itself, would make the program more portable (which is kinda of the point of "portable" distributions), allowing you to have the program AND its configuration together on a USB drive or ... .

2- This would also make it possible to have different instances of the program with different configurations in different directories on the same system, allowing you to keep and rapidly switch between multiple configurations (which again, is kind of the point of having portable distributions).

3- This would allow the program configuration to survive OS changes (Or be usable in different OS's in a multi-boot setup), by having this program (alongside your other portable programs) on a different partition than your OS partition (again, one of the points of portable distributions).

Other VPN / Proxy programs also typically store their configuration in the program directory itself, in their portable distributions.

Thanks

[ircfspace]

Hi,
You’ve made a good point.
We’ll address this issue in future updates.

[Dr-Bad]

@ircfspace
I'm going to make a pull request for this.
Would it be okay to move everything related to oblivion inside assets folder on all platforms?

[ircfspace]

@Dr-Bad I started working on this task a few days ago, but I discarded my changes.
The app has millions of users, so any new modifications must not cause issues for existing users after they update.

It’s not just about changing the file paths; we also need to make sure that the existing configuration files like sbConfig, Masque config, settings.json, windowPosition.json, and ver.txt are moved to the new assets directory without losing user data.

Another key point is that the app should still run without requiring admin privileges by default. If a user installs it under Program Files or similar directories, read/write access to assets could become a problem.

I remember that in the early versions, we kept files like warp-plus inside assets/bin, but we later moved them to userData exactly because of those permission issues.

Given all these conditions and complexities, if you’re ready to take on this feature and its challenges; that would be great.

[Dr-Bad]

So, I think there are two possible solutions:

1. only change the path for portable builds and leave the rest of the builds untouched.

2. Finding a solution for permission issues and creating a migration script to copy data from appData to local environment.

[ircfspace]

only change the path for portable builds and leave the rest of the builds untouched

Yeah, maybe this is the better option.