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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe "normal" Mac convention is to store configuration data in a folder under username/Library/Application Support/Appname
So username/Library/Application Support/Amiberry
If the amiberry.conf was copied to here and this was the "live" version that Amiberry looked for then that solves the problem.
That amiberry.config could still by default point to a set of folders in username/Documents/Amiberry, but could then easily be reconfigured by the user to point somewhere else, as they already can.
Basically, move the amiberry.conf file from username/Documents/Amiberry/Configuration/Amiberry.conf to username/Library/Application Support/Amiberry/Amiberry.conf :)
* refactor: use separate dir for amiberry.conf and data under macOS (#1372)
Moving the contents of the data folder and amiberry.conf, under <user>/Library/Application Support/Amiberry for macOS platforms
* refactor: use separate dir for amiberry.conf and data under macOS (#1372)
Moving the contents of the data folder and amiberry.conf, under <user>/Library/Application Support/Amiberry for macOS platforms
I believe "normal" Mac convention is to store configuration data in a folder under username/Library/Application Support/Appname
So username/Library/Application Support/Amiberry
If the amiberry.conf was copied to here and this was the "live" version that Amiberry looked for then that solves the problem.
That amiberry.config could still by default point to a set of folders in username/Documents/Amiberry, but could then easily be reconfigured by the user to point somewhere else, as they already can.
Basically, move the amiberry.conf file from username/Documents/Amiberry/Configuration/Amiberry.conf to username/Library/Application Support/Amiberry/Amiberry.conf :)
Originally posted by @StusBrainDump in #1370 (reply in thread)
The text was updated successfully, but these errors were encountered: