I have read many entries in this forum regarding the preferences file and what you can and cannot change in it for the sake of troubleshooting and just for OCD. However, it is only referenced in brief, implicit terms (eg. “just rename the prefs file!”) and my testing has turned out completely backwards results.
What I would like to know, ideally in the form of formal documentation and not just an offhanded comment, is what I can and cannot change after the creation of a storage, repository, etc… My first and only assumption is that the only way to accomplish any of this is through the editing of the preferences file (though a formally supported and UI-enabled feature would obviously be preferred).
Things that are currently tripping me up:
It appears CLI vs WebUI write the contents of the .duplicacy folder differently and store them in different places (CLI in the root of the repository vs the centralized location with the WebUI).
The contents of each preferences file contain many entries (one for each storage, it appears) so any one repository or storage is actually mentioned multiple times in multiple places.
There is a preferences file both at the repository level and in “all” (which look to contain different information)
(the big one) No matter what I change in the prefs file, after I run a command from the WebUI, it reverts all changes in the prefs file back to the original values.
Why I’d like to do any of this is for the sake of troubleshooting (there are many mentions of this by gchen (developer) as being the preferred method to get yourself out of trouble in various scenarios), moving location of a repository or storage, and just for the sake of organization as my usage of Duplicacy grows and original plans, naming conventions, etc. no longer make sense.
My shallow understanding of lock-free tells me this shouldn’t technically cause issues as long as you’re being smart about it. I also see this as a (possibly) simple addition to the actual WebUI, and definitely something that if formally implemented in the UI would be very easy for users to understand and take advantage of.
Any information or suggestions on this would be very helpful. And aside from my specific needs, given how much I see subtle references to this in the forum, it feels like it should be formally documented in some way. …And apologies if this is explained somewhere. I have been on these forums for months and have read nearly every entry with the tag “preferences” “rename” etc.