Repository navigation
Custom configuration file location #2787
Description
Activity
I need to check this again. I have removed it in the past because there were too many problems with this feature.
since I have an issue next to a profile copied to Onedrive, this feature will be a must have
I will try to implement it when i am done with #3144
Just changing the path should be easy. For now i think it makes sense to just copy/past the existing profiles + settings to the new location after changing the path... merging them was such a pain the past (overwrite, keep existing version, etc.)... that's why the feature was removed...
Maybe with the Backup & Import feature this will be more easy - it's alredy on the roadmap: #2700 #2679.
@thongor77 @CNLancer-Yoo what are the use cases you have?
Does it make more sense to let the user configure the path (in the UI)? Or maybe the IT department via a registry key / shortcut parameter?
For the portable version this option should be ignored / disabled. So it's only relevant for the installer / archive.
Implemented for the application settings (user can select it OR system wide policy). Will be available soon as a pre-release. #3324
I will implement it now for the profile files... most of the work is already done.
Implemented in #3340.
The profile folder path can now be changed via the UI or a Policy (
config.json). I will release a new version later or tomorrow.Edit: Released in https://github.com/BornToBeRoot/NETworkManager/releases/tag/2026.2.22.0
Request to add a new feature, "Custom configuration file location". I would like to place the configuration file in a different drive letter. thank you
